Skip to content

Conversation

stefanb
Copy link
Member

@stefanb stefanb commented Feb 11, 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>?

Follow-up to:

Upstream issue:

@stefanb stefanb added the CI-no-bottles Merge without publishing bottles label Feb 11, 2025
@stefanb stefanb force-pushed the ethereum-pin-to-go-1.23 branch from 611ae1b to bd35880 Compare February 11, 2025 16:39
@github-actions github-actions bot added the go Go use is a significant feature of the PR or issue label Feb 11, 2025
@stefanb stefanb changed the title ethereum: pin to go 1.23 (go 1.24) ethereum: pin to go@1.23 (go 1.24) Feb 11, 2025
@stefanb stefanb force-pushed the ethereum-pin-to-go-1.23 branch from bd35880 to 28cdb37 Compare February 13, 2025 04:25
@stefanb stefanb removed the blocked label Feb 13, 2025
@stefanb stefanb marked this pull request as ready for review February 13, 2025 04:26
@BrewTestBot BrewTestBot added this pull request to the merge queue Feb 13, 2025
Merged via the queue into master with commit 0f103ca Feb 13, 2025
25 checks passed
@BrewTestBot BrewTestBot deleted the ethereum-pin-to-go-1.23 branch February 13, 2025 04:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI-no-bottles Merge without publishing bottles go Go use is a significant feature of the PR or issue
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants