Skip to content

Drop the polyfill for native workspace APIs - #14

Draft
grouville wants to merge 1 commit into
dagger:mainfrom
grouville:polyfill-removal
Draft

Drop the polyfill for native workspace APIs#14
grouville wants to merge 1 commit into
dagger:mainfrom
grouville:polyfill-removal

Conversation

@grouville

@grouville grouville commented Aug 7, 2026

Copy link
Copy Markdown
Member

The Python SDK no longer needs dagger/polyfill.

Managed modules now come from currentModule.asSDK(workspace: ws).modules, which uses the registrations already present in dagger.toml. Generation uses ModuleSource.generate(workspace) and all edits compose on the supplied workspace before one final .changes call.

The behavior stays cwd-aware; the engine now owns the isolation and path conversion previously implemented by the wrapper.

Test

dagger check 'e-2-e:*'

Signed-off-by: Guillaume de Rouville <guillaume@dagger.io>
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