Skip to content

Conversation

stefanb
Copy link
Member

@stefanb stefanb commented Jul 27, 2025

  • Have you followed the guidelines for contributing?
  • Have you ensured that your commits follow the commit style guide?
  • Have you checked that there aren't other open pull requests for the same formula update/change?
  • Have you built your formula locally with HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>, where <formula> is the name of the formula you're submitting?
  • Is your test running fine brew test <formula>, where <formula> is the name of the formula you're submitting?
  • Does your build pass brew audit --strict <formula> (after doing HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>)? If this is a new formula, does it pass brew audit --new <formula>?

found in

@stefanb stefanb added upstream issue An upstream issue report is needed checksum mismatch SHA-256 doesn't match the download labels Jul 27, 2025
@github-actions github-actions bot added the go Go use is a significant feature of the PR or issue label Jul 27, 2025
@chenrui333
Copy link
Member

image

@stefanb
Copy link
Member Author

stefanb commented Jul 28, 2025

Thanks @chenrui333!

This workflow execution log confirms, that the same git tag v0.29.0 was present on at least three different commits.

It is not known it the github release was also created three times, but that is less likely and it would perhaps help to enable github_latest strategy in the formula. Opinions?

@chenrui333
Copy link
Member

It is not known it the github release was also created three times, but that is less likely and it would perhaps help to enable github_latest strategy in the formula. Opinions?

Sounds good to me 👍

@stefanb stefanb force-pushed the buildpulse-test-reporter-update-checksum branch from cd03f85 to 6bfaa5b Compare July 30, 2025 06:21
@stefanb
Copy link
Member Author

stefanb commented Jul 30, 2025

Updated livecheck to strategy :github_latest.
Do we still want/need some confirmation from upstream about obvious tag moving?

@chenrui333 chenrui333 added the CI-checksum-change-confirmed A checksum change was confirmed by upstream label Jul 30, 2025
@chenrui333
Copy link
Member

I think we can keep the upstream issue for comms and move forward fixing the checksum mismatch.

Copy link
Contributor

🤖 An automated task has requested bottles to be published to this PR.

Caution

Please do not push to this PR branch before the bottle commits have been pushed, as this results in a state that is difficult to recover from. If you need to resolve a merge conflict, please use a merge commit. Do not force-push to this PR branch.

@github-actions github-actions bot added the CI-published-bottle-commits The commits for the built bottles have been pushed to the PR branch. label Jul 30, 2025
@BrewTestBot BrewTestBot enabled auto-merge July 30, 2025 11:36
@BrewTestBot BrewTestBot added this pull request to the merge queue Jul 30, 2025
Merged via the queue into main with commit 3d76608 Jul 30, 2025
22 checks passed
@BrewTestBot BrewTestBot deleted the buildpulse-test-reporter-update-checksum branch July 30, 2025 11:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
checksum mismatch SHA-256 doesn't match the download CI-checksum-change-confirmed A checksum change was confirmed by upstream CI-published-bottle-commits The commits for the built bottles have been pushed to the PR branch. go Go use is a significant feature of the PR or issue upstream issue An upstream issue report is needed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants