Install Monarch from release binaries - #3
Merged
Conversation
matteing
marked this pull request as ready for review
July 26, 2026 11:36
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
1 participant
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.
What changed
checksums.txt.miseare not required for installation.Why
The previous installation instructions exposed the contributor toolchain as though it were an end-user prerequisite. The existing GoReleaser pipeline already produces self-contained cross-platform archives, so installation should consume those artifacts directly.
Impact
Users can install Monarch without setting up Go or
mise. An initialv*release tag still needs to be published before the latest-release link has an artifact to download.Validation
go test ./...mise run release:checkgit diff --check