Skip to content

Keep the runtime for an engineVersion past the target - #27

Draft
eunomie wants to merge 1 commit into
entrypoint-guard-cachingfrom
entrypoint-guard-engine-version
Draft

eunomie wants to merge 1 commit into
entrypoint-guard-cachingfrom
entrypoint-guard-engine-version

Conversation

@eunomie

@eunomie eunomie commented Nov 11, 2026

Copy link
Copy Markdown
Member

Stacked on the previous pull request. Migration drops a manifest engineVersion, which would move a module created by a newer CLI back across the identifier-casing cut. A manifest engineVersion later than targetEngineVersion now keeps the module on the runtime. A module already on the entrypoint is not refused: the engine reads such a module's version from dang.toml, not from the manifest (engine v1.0.0-beta.27, resolveModuleSourceVersions). The test uses v1.1.0, so it holds for both the current and the beta.27 target.

Checks, on the beta.27 engine and CLI: entrypoint-migration-check, target-version-check and entrypoint-ownership-check passed. Not proved: the dagger.json reading path with a later version.

Migration would silently drop a manifest engineVersion later than the
target, a version the SDK cannot generate for. A module already on the
entrypoint is not refused: the engine reads its dang.toml version.

Signed-off-by: Yves Brissaud <yves@dagger.io>
@eunomie
eunomie force-pushed the entrypoint-guard-engine-version branch from dc0f07d to cc9083d Compare November 11, 2026 14:31
@eunomie
eunomie added this pull request to stack #32 November 11, 2026 14:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant