terramaid: update checksum for 2.15.3 release#290269
Closed
stefanb wants to merge 1 commit into
Closed
Conversation
stefanb
added
upstream issue
github-actions
Bot
added
the
go
stefanb
force-pushed
the
terramaid-update-checksum
branch
from
June 28, 2026 05:25
9135233 to
76e1d5c
Compare
stefanb
added a commit
that referenced
this pull request
Jul 1, 2026
Autobump disabled because upstram bumps it as needed: https://github.com/RoseSecurity/Terramaid/blob/26ceb1eaae1a52b264f099dc9a7f37a6d2a5a08c/.github/workflows/build.yaml#L124-L127 ```yaml - uses: dawidd6/action-homebrew-bump-formula@1446dca # v7 with: # A PR will be sent to github.com/Homebrew/homebrew-core to update this formula: formula: terramaid ``` and this was [failing](https://github.com/RoseSecurity/Terramaid/actions/runs/27016781794/job/79734376960#step:4:117) with: ``` Error: Whoops, the terramaid formula has its version update pull requests automatically opened by BrewTestBot every ~3 hours! We'd still love your contributions, though, so try another one that is excluded from autobump list (i.e. it has 'no_autobump!' method or 'livecheck' block with 'skip'.) ``` Spin-off from * #290269
stefanb
changed the title
stefanb
force-pushed
the
terramaid-update-checksum
branch
from
July 1, 2026 16:27
76e1d5c to
82d85d6
Compare
Member
|
Since it's closed without comment let's assume they won't make stable releases and disable the formula |
Member
Author
|
They gave a reference to some internal ticket, with no further info 🤷 It averages 2-3 installs per day. 🤔 |
Member
Author
|
They confirmed upstream deprecation, so i opened |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Could not find clear evidence of retagging in https://github.com/RoseSecurity/Terramaid/actions to determine the diff, just that https://github.com/RoseSecurity/Terramaid/actions/runs/27016781794 was run on RoseSecurity/Terramaid@f63974a,
but the release https://github.com/RoseSecurity/Terramaid/releases/tag/v2.15.3 currently points to RoseSecurity/Terramaid@45b727e which does not belong to any branch on this repository:
Tags:
Diff RoseSecurity/Terramaid@f63974a...45b727e is empty.
Ref:
HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>?brew test <formula>?brew audit --strict <formula>(after doingHOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>)? If this is a new formula, does it passbrew audit --new <formula>?