Pipeline re-uploads assets without re-triggering homebrew formula update
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
Start by tracing the release pipeline step that updates the cloudfoundry/homebrew-tap formula and how it is triggered when release assets are uploaded or replaced. Check the pipeline configuration and related tests; reproduce or inspect a rerun that replaces assets. Done when replacing release assets also refreshes the formula checksums so brew upgrade bbl succeeds.
Written by the indexing model from the issue text.
Description
Summary
When the release pipeline re-runs and replaces assets on an existing release, the cloudfoundry/homebrew-tap formula update step does not re-run. This leaves bbl.rb with stale checksums that cause brew upgrade bbl to fail for all users with a SHA256 mismatch error.
What happened (v9.0.50)
- 2026-09-30 — pipeline cut the v9.0.50 release and uploaded initial assets
- 2026-10-01 — BOSH CI committed the homebrew formula with checksums from those assets
- 2026-10-05 — pipeline re-ran (triggered by commit
bf54483b, "Update deployments"), rebuilt all binaries, re-uploaded all assets, and updated the release tag — but did not re-trigger the homebrew formula update
All five release assets were replaced with new binaries (likely picking up an updated bundled terraform version). The formula was never updated, so the expected checksum (c2c986fa... for osx_arm64) no longer matches the actual download (2f5b3b00...).
Impact
brew upgrade bbl fails for all users:
Error: Formula reports different checksum: c2c986fa97b501973217b4a868414a8c65698290b893480c86c610c04439c880
SHA-256 checksum of downloaded file: 2f5b3b004be3aa757d21b0e59afb5e8d82c2791cec3df1dd118110da16ae9bc1
- Dominant language
- Go
- Stars
- 181
- Forks
- 179
- Avg merge
- 9h 54m
- Merged PRs (30d)
- 2
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from cloudfoundry/bosh-bootloader
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
cloudfoundry/bosh-bootloader#701 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 58/100
cloudfoundry/bosh-bootloader#681 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
cloudfoundry/bosh-bootloader#676 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
cloudfoundry/bosh-bootloader#641 · 2 comments ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 50/100
cloudfoundry/bosh-bootloader#636 · 2 comments ·
All issues in cloudfoundry/bosh-bootloader
Similar issues
-
agent-butler-finding bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
jordansmall/spindrift#6414 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Icinga/icinga-kubernetes#294 ·
Maintainers usually reply within 4 days
-
Cluster details: the Control Plane version field has a different border color than its icon boxOpenkind/design sig/ui
Difficulty 1/5 Under an hour Newbie friendliness 92/100
kubermatic/dashboard#8449 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
filecoin-project/curio#1632 ·
Maintainers usually reply within 1 day