[wip] automate versioned Homebrew formula publishing #863
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.
This is the initial, simpler solution to #862 which assumes we continue to publish src-cli the way we typically have, i.e. only ever releasing a new latest version. It assumes that the newer a tag is, the later the version is. This is absolutely not a good assumption to make most of the time, however it turns out to be remarkably realistic for our repository. With the exception of the 4.0.0-rc release, we have not had a patch release on an older major version since March of 2020.
It adds a
goreleaser-prestep which:It then lets
goreleaserrun like normal, which will update the main Homebrew formula.It then also adds a
goreleaser-poststep which:Test plan
goreleaserstep (don't want to actually publish anything new), point pre and post steps at fork repo