Skip to content

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

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#30
yeazelm merged 1 commit into
mainfrom
dagger_8/bump-engine-v0.20.8

Conversation

@yeazelm
Copy link
Copy Markdown
Contributor

@yeazelm yeazelm commented May 13, 2026

Summary

  • The release pipeline has been failing because the engine pinned in each module's 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 every module (bucketupload, checksum, ghcontrib, ghrelease, go, golangcilint, utils) and DAGGER_VERSION in the PR workflow to v0.20.8, matching the rest of the org repos (e.g. paper PR #40) that have already moved.

Refs PCC-543

Test plan

  • PR workflow passes on this PR
  • Downstream consumers (paper, tapes-extproc, etc.) keep working after this merges

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 each module's `dagger.json` and the
`DAGGER_VERSION` env in the PR workflow 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:52
@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 fixes a failing release pipeline by synchronizing the Dagger engine version across all modules and the CI workflow, bumping from v0.20.6 to v0.20.8.

  • All seven module dagger.json files (bucketupload, checksum, ghcontrib, ghrelease, go, golangcilint, utils) have their engineVersion updated from v0.20.6 to v0.20.8.
  • The DAGGER_VERSION env var in .github/workflows/pr.yaml is updated to match, ensuring the CLI installed by dagger-for-github aligns with the engine pinned in each module.

Confidence Score: 5/5

Safe to merge β€” all changes are a uniform version string update with no logic modifications.

Every changed file performs exactly the same mechanical update: replacing the Dagger version string from v0.20.6 to v0.20.8. The workflow env var and all seven module manifests are updated consistently, leaving no version mismatch between the CLI installer and the module engine pins.

No files require special attention.

Important Files Changed

Filename Overview
.github/workflows/pr.yaml Bumps DAGGER_VERSION env var from 0.20.6 to 0.20.8 to match module engine versions
bucketupload/dagger.json engineVersion bumped from v0.20.6 to v0.20.8
checksum/dagger.json engineVersion bumped from v0.20.6 to v0.20.8
ghcontrib/dagger.json engineVersion bumped from v0.20.6 to v0.20.8
ghrelease/dagger.json engineVersion bumped from v0.20.6 to v0.20.8
go/dagger.json engineVersion bumped from v0.20.6 to v0.20.8
golangcilint/dagger.json engineVersion bumped from v0.20.6 to v0.20.8
utils/dagger.json engineVersion bumped from v0.20.6 to v0.20.8

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[PR Workflow Triggered] --> B[dagger-for-github installs CLI\nDAGGER_VERSION=0.20.8]
    B --> C{CLI ↔ Engine\nVersion Handshake}
    C -->|v0.20.6 - FAIL| D[❌ Pipeline fails before\nuser code is reached]
    C -->|v0.20.8 - PASS| E[βœ… dagger call proceeds]
    E --> F[bucketupload\nv0.20.8]
    E --> G[checksum\nv0.20.8]
    E --> H[ghcontrib\nv0.20.8]
    E --> I[ghrelease\nv0.20.8]
    E --> J[go\nv0.20.8]
    E --> K[golangcilint\nv0.20.8]
    E --> L[utils\nv0.20.8]
Loading

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

@yeazelm yeazelm merged commit 99a176a into main May 13, 2026
4 checks passed
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