dagger/dagger · error

determine latest released version: %w

Error message

determine latest released version: %w

What it means

Wraps a failure from latestVersion while running 'dagger mod require-latest', which resolves the latest released engine version and pins it in the module config. The lookup (typically a network call to release metadata) failed, so the module version cannot be set.

Source

Thrown at internal/cmd/dagger/module_cmd.go:213

	Use:     "require <version>",
	Short:   "Set the module's required engine version",
	Example: "dagger module engine require v0.21.0",
	Args:    cobra.ExactArgs(1),
	RunE: func(cmd *cobra.Command, args []string) error {
		return withEngine(cmd.Context(), client.Params{}, func(ctx context.Context, engineClient *client.Client) error {
			return setModuleEngineVersion(ctx, cmd.OutOrStdout(), engineClient.Dagger(), args[0])
		})
	},
}

var moduleEngineRequireLatestCmd = &cobra.Command{
	Use:   "require-latest",
	Short: "Set the module's required engine version to the latest released version",
	Args:  cobra.NoArgs,
	RunE: func(cmd *cobra.Command, _ []string) error {
		latest, err := latestVersion(cmd.Context())
		if err != nil {
			return fmt.Errorf("determine latest released version: %w", err)
		}
		return withEngine(cmd.Context(), client.Params{}, func(ctx context.Context, engineClient *client.Client) error {
			return setModuleEngineVersion(ctx, cmd.OutOrStdout(), engineClient.Dagger(), latest)
		})
	},
}

var moduleEngineRequireCurrentCmd = &cobra.Command{
	Use:   "require-current",
	Short: "Set the module's required engine version to the currently running engine version",
	Args:  cobra.NoArgs,
	RunE: func(cmd *cobra.Command, _ []string) error {
		return withEngine(cmd.Context(), client.Params{}, func(ctx context.Context, engineClient *client.Client) error {
			dag := engineClient.Dagger()
			current, err := dag.Version(ctx)
			if err != nil {
				return fmt.Errorf("determine current engine version: %w", err)
			}

View on GitHub (pinned to 82ba2681db)

Solutions

1. Check network/proxy access to the release metadata source
2. Pin a version explicitly instead (edit dagger.json engine version or use require with a specific version)
3. Retry later if the release service is temporarily down

Example fix

// before (offline)
dagger mod require-latest
// determine latest released version: ...
// after: pin explicitly
dagger mod require v0.15.0  # or edit dagger.json engineVersion

// quick reachability probe before resolving latest
resp, err := http.Head(releaseMetaURL)
if err != nil || resp.StatusCode != 200 {
	return errors.New("release metadata endpoint unreachable")
}

latest, err := latestVersion(ctx)
if err != nil {
	if pin := pinnedFallbackVersion(); pin != "" {
		return setModuleEngineVersion(ctx, out, dag, pin)
	}
	return fmt.Errorf("determine latest released version: %w", err)
}

When it happens

Trigger: Running 'dagger mod require-latest' when latestVersion(cmd.Context()) fails — unreachable release endpoint, offline machine, proxy blocking the request, or malformed release data.

Common situations: Corporate proxy/firewall blocking GitHub releases; DNS failure; running fully offline; a broken release metadata endpoint.

Related errors

• determine current engine version: %w
• invalid value %s
• bridge from cidr: %w
• ensure iptables symlinks: %w
• install resolv.conf: %w

AI-assisted analysis of dagger/dagger@82ba2681db (2026-09-05). Data as JSON: /api/errors/f1b655dee68aadfe. Report an issue: GitHub.