Repository navigation
feat: add version flags and automate tagged releases - #25
Merged
Merged
Conversation
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
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.
Add
ridlfmt -versionandridlfmt -vto print the installed version and exit before reading input. Prefer a version injected at build time, then Go's embedded module version, withdevelas the fallback. Align CLI help and update the README usage example.Match webrpc's tag-based release approach:
make buildandmake installstamp the version fromgit describe --tags --dirty, with an explicitVERSIONoverride and a fallback for checkouts without tags. Pushing av*tag runs tests and GoReleaser to publish macOS, Linux, and Windows binaries for amd64 and arm64, checksums, and generated release notes.Validation:
go test ./...andgit diff --checkpass.Closes #13