buildpulse-test-reporter: update checksum

[stefanb]

• 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

• go 1.25.0, go@1.24 1.24.6 (new formula) #226636

[chenrui333]

[stefanb]

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]

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]

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

[chenrui333]

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

[github-actions]

🤖 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.