Skip to content

Keep the runtime when migration drops caching or clients - #26

Draft
eunomie wants to merge 1 commit into
composer-checkfrom
entrypoint-guard-caching
Draft

eunomie wants to merge 1 commit into
composer-checkfrom
entrypoint-guard-caching

Conversation

@eunomie

@eunomie eunomie commented Nov 11, 2026

Copy link
Copy Markdown
Member

Migration to the generated entrypoint (usesEntrypoint) now keeps a module on the PHP runtime when it sets disableDefaultFunctionCaching: true or records clients: a version 2 manifest ignores both keys, so migration silently turned caching on or dropped the clients. A module already on the entrypoint with either setting is refused through the existing branch. README lists the new reasons.

Checks, on the beta.27 engine and CLI: entrypoint-migration-check (three new assertions and one refusal) and entrypoint-ownership-check passed. Not proved: a clients entry in a real dagger.json; observing a migrated module's caching.

A version 2 manifest ignores these keys, so migration silently turned
caching on or dropped the clients.

Signed-off-by: Yves Brissaud <yves@dagger.io>
@eunomie
eunomie force-pushed the entrypoint-guard-caching branch from 427c4da to ad4170c Compare November 11, 2026 14:31
@eunomie
eunomie changed the base branch from main to composer-check November 11, 2026 14:32
@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