Dagger Changeset API merges changesets
Introduced 2026-02-05 · score 0.97
HOW TO USE IT
When combining changesets from module functions, call `withChangeset` for one changeset or `withChangesets` for several. Choose a supported `onConflict` value when conflicts need handling; the plural method supports only `FAIL` and `FAIL_EARLY` in v0.19.11.
changeset.withChangeset(changes: <otherChangeset>, onConflict: <strategy>)changeset.withChangesets(changes: [<otherChangeset1>, <otherChangeset2>], onConflict: <pluralStrategy>)WHY THIS HELPS
Combine changesets produced by module functions while resolving conflicting file changes.
REQUIREMENTS AND LIMITATIONS
- Version: v0.19.11
- withChangeset.changes (required): Changeset to merge into the calling changeset.
- withChangeset.onConflict: Conflict strategy; defaults to `FAIL`. Allowed: `FAIL_EARLY`, `FAIL`, `LEAVE_CONFLICT_MARKERS`, `PREFER_OURS`, `PREFER_THEIRS`.
- withChangesets.changes (required): List of changesets to merge into the calling changeset.
- withChangesets.onConflict: Conflict strategy; defaults to `FAIL`. Allowed: `FAIL_EARLY` or `FAIL` only; the strategies are mutually exclusive enum values.
- Merging uses git under the hood.
- The linked description says conflicts raise an error by default; `onConflict` can be set to `fail`, `skip`, `preferSelf`, or `preferOther`.
- Docs conflict: The v0.19.11 schema documents `withChangeset` (singular) and `withChangesets` (plural); the card's `withChangset` spelling is not the documented method name.
- Docs conflict: `withChangesets` in v0.19.11 does not support all four card-listed strategies: its schema allows only `FAIL` and `FAIL_EARLY`. `withChangeset` uses the five values documented above.
FIRST-PARTY EVIDENCE
- https://github.com/dagger/dagger/releases/tag/v0.19.11
- https://github.com/dagger/dagger/pull/11577
- https://github.com/dagger/dagger/blob/v0.19.11/docs/docs-graphql/schema.graphqls
Check the installed version and the source before using it. Entry JSON