Skip to content

Drop the polyfill for the engine's findConfigDirs - #42

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

Drop the polyfill for the engine's findConfigDirs#42
grouville wants to merge 1 commit into
dagger:mainfrom
grouville:polyfill-removal

Conversation

@grouville

Copy link
Copy Markdown
Member

Migrates this repo off github.com/dagger/polyfill, onto the engine's own workspace APIs — part of dagger/dagger#13769 (tracking checklist there; engine PRs dagger/dagger#13854 and dagger/dagger#13855).

One call site: polyfill.workspace(ws).findConfigDirs(...) becomes ws.findConfigDirs(...) — same semantics, the engine API was ported from the polyfill's own design and test matrix.

Verified locally against a dev engine built from the two engine PRs: dagger check 'e-2-e:*' — 9/9 passed (discovery, generate, selection, per-module directives).

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 engine now ships Workspace.findConfigDirs (dagger/dagger#13769):
the same cwd-aware project discovery this module got from
github.com/dagger/polyfill — same semantics, ported from the
polyfill's own design and test matrix. Swap the call, drop the
dependency, and require the engine release that ships it.

The engineVersion bump and the dependency removal have to land
together: the version gate is what keeps the engine's new changeset
behavior scoped to migrated modules.

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