Pipeline re-uploads assets without re-triggering homebrew formula update

未关闭
#698 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
48/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
go
领域
release

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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)

  1. 2026-09-30 — pipeline cut the v9.0.50 release and uploaded initial assets
  2. 2026-10-01 — BOSH CI committed the homebrew formula with checksums from those assets
  3. 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
主要语言
Go
星标
181
派生
179
平均合并
9 小时 54 分钟
30 天内合并 PR
2

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

cloudfoundry/bosh-bootloader 的其他 Issue

查看 cloudfoundry/bosh-bootloader 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。