Skip to content

πŸ”§ fix: bump dagger v0.20.6 β†’ v0.20.8#55

Merged
yeazelm merged 1 commit into
mainfrom
dagger_8/bump-engine-v0.20.8
May 13, 2026
Merged

πŸ”§ fix: bump dagger v0.20.6 β†’ v0.20.8#55
yeazelm merged 1 commit into
mainfrom
dagger_8/bump-engine-v0.20.8

Conversation

@yeazelm
Copy link
Copy Markdown
Collaborator

@yeazelm yeazelm commented May 13, 2026

Summary

  • The release pipeline has been failing because the engine pinned in dagger.json (v0.20.6) and the CLI installed by dagger-for-github no longer round-trip cleanly with the current daggerverse modules. The version handshake fails before dagger call reaches user code.
  • Bumps engineVersion in dagger.json and DAGGER_VERSION in all workflows to v0.20.8, matching the rest of the org repos (e.g. paper PR 🧹 chore: fixup for cutting release with bot appΒ #40) that have already moved.

Refs PCC-543

Test plan

  • CI workflow passes on this PR
  • Release / cut-release workflows succeed on the next tag push

Release pipeline has been failing because the engine pinned in
`dagger.json` (v0.20.6) and the CLI installed by `dagger-for-github`
no longer round-trip cleanly with the current daggerverse modules β€” the
version handshake fires before `dagger call` reaches the user code, so
every PR / CI / cut-release / release run dies in the bootstrap step.

Bumps `engineVersion` in `dagger.json` and the matching `DAGGER_VERSION`
env in all workflows to v0.20.8, matching the rest of the org's repos
that have already moved.

Refs PCC-543
@yeazelm yeazelm requested a review from a team May 13, 2026 20:48
@linear-code
Copy link
Copy Markdown

linear-code Bot commented May 13, 2026

PCC-543

@greptile-apps
Copy link
Copy Markdown

greptile-apps Bot commented May 13, 2026

Greptile Summary

This PR bumps the Dagger version from v0.20.6 to v0.20.8 across all GitHub Actions workflows and dagger.json to resolve a version handshake failure that was breaking the release pipeline.

  • dagger.json: engineVersion updated from v0.20.6 to v0.20.8, keeping the engine pin in sync with the CLI.
  • All 5 workflows (ci.yaml, cut-release.yaml, nightly.yaml, pr.yaml, release.yaml): DAGGER_VERSION env var updated consistently to 0.20.8.

Confidence Score: 5/5

All six files receive a single, identical version-string change that is consistent throughout the PR β€” safe to merge.

The change is a mechanical, uniform version bump applied identically to every workflow file and the engine pin in dagger.json. The CLI version and the engine version now agree, which is exactly what the Dagger version-handshake requires. No logic, permissions, secrets handling, or workflow structure was touched.

No files require special attention.

Important Files Changed

Filename Overview
dagger.json Bumps engineVersion from v0.20.6 to v0.20.8 to match the updated CLI version in all workflows.
.github/workflows/ci.yaml Bumps DAGGER_VERSION env var from 0.20.6 to 0.20.8; no other changes.
.github/workflows/cut-release.yaml Bumps DAGGER_VERSION env var from 0.20.6 to 0.20.8; no other changes.
.github/workflows/nightly.yaml Bumps DAGGER_VERSION env var from 0.20.6 to 0.20.8; no other changes.
.github/workflows/pr.yaml Bumps DAGGER_VERSION env var from 0.20.6 to 0.20.8; no other changes.
.github/workflows/release.yaml Bumps DAGGER_VERSION env var from 0.20.6 to 0.20.8; no other changes.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["dagger-for-github\n(CLI v0.20.8)"] --> B{"Version handshake\nCLI == engineVersion?"}
    B -- "βœ… Match (v0.20.8)" --> C["dagger call proceeds"]
    B -- "❌ Mismatch (was v0.20.6)" --> D["Handshake failure\nPipeline aborted"]
    C --> E["ci / pr / nightly / release / cut-release"]

    style D fill:#f88,color:#000
    style C fill:#8f8,color:#000
Loading

Reviews (1): Last reviewed commit: "πŸ”§ fix: bump dagger v0.20.6 β†’ v0.20.8" | Re-trigger Greptile

@yeazelm yeazelm merged commit 7f06f11 into main May 13, 2026
13 checks passed
@yeazelm yeazelm deleted the dagger_8/bump-engine-v0.20.8 branch May 13, 2026 21:58
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.

2 participants