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

Copy link
Copy Markdown
Member

Migrates this module off github.com/dagger/polyfill — part of dagger/dagger#13769 (tracking checklist there; engine PRs dagger/dagger#13854 and dagger/dagger#13855).

The only polyfill surface used here is moduleSource: Workspace.moduleSource covers it, with contextDirectory / sourceRootSubpath in place of the polyfill's workspaceView / sourceRootPath.

Verified locally against a dev engine built from the two engine PRs: dagger check22/22 passed.

CI stays red until the engine release that ships these APIs exists. The engineVersion bump assumes v1.0.0-beta.10 — adjust if the release numbers differently. The bump and the dependency removal must land together: the version gate is what scopes the engine's new changeset rooting to migrated modules.

The only polyfill surface this module used is moduleSource
(dagger/dagger#13769): Workspace.moduleSource covers it, with
contextDirectory / sourceRootSubpath in place of the polyfill's
workspaceView / sourceRootPath.

The engineVersion bump and the dependency removal land together, like
the SDK migrations this module black-box-tests.

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