Skip to content

ratify: fix checksum for 1.4.0 #207036

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 2 commits into from
Feb 11, 2025
Merged

ratify: fix checksum for 1.4.0 #207036

merged 2 commits into from
Feb 11, 2025

Conversation

stefanb
Copy link
Member

@stefanb stefanb commented Feb 9, 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 the checksum mismatch SHA-256 doesn't match the download label Feb 9, 2025
@github-actions github-actions bot added the go Go use is a significant feature of the PR or issue label Feb 9, 2025
@stefanb stefanb mentioned this pull request Feb 9, 2025
Merged
39 tasks
@daeho-ro
Copy link
Member

daeho-ro commented Feb 9, 2025

Bump is included later,

image

@stefanb stefanb added the CI-checksum-change-confirmed A checksum change was confirmed by upstream label Feb 9, 2025
@SMillerDev
Copy link
Member

Did they retag?

@stefanb
Copy link
Member Author

stefanb commented Feb 9, 2025

@SMillerDev yes, it can be seen in the screenshot from @daeho-ro, that the v1.4.0 tag was at 2 different commits.

@SMillerDev
Copy link
Member

Sure, but that doesn't confirm that upstream meant to do it. It only confirms that it happened.

@stefanb stefanb removed the CI-checksum-change-confirmed A checksum change was confirmed by upstream label Feb 9, 2025
@daeho-ro daeho-ro mentioned this pull request Feb 9, 2025
Closed
1 task
@daeho-ro daeho-ro added the CI-checksum-change-confirmed A checksum change was confirmed by upstream label Feb 11, 2025
@github-actions GitHub Actions
Copy link
Contributor

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

@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 Feb 11, 2025
@BrewTestBot BrewTestBot added this pull request to the merge queue Feb 11, 2025
Merged via the queue into master with commit 6a93bca Feb 11, 2025
15 checks passed
@BrewTestBot BrewTestBot deleted the ratify-fix-checksum branch February 11, 2025 12:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@bevanjkay bevanjkay bevanjkay approved these changes

@github-actions github-actions[bot] github-actions[bot] approved these changes

Assignees
No one assigned
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
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
5 participants
@stefanb @daeho-ro @SMillerDev @bevanjkay @BrewTestBot