chore: Automate version file control and fix goreleaser #304
Conversation
This file contains 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
nieomylnieja
changed the title
…tl into automate-version-file-control
This was referenced Mar 11, 2025
Merged
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.
Summary
Turns
runtime/debugpackage allows us to seeBuildInfowhich among other things has details about the main module's version. The version is set bygo install, for prebuilt binaries withgo buildwe're leaving the process intact.I haven't tested how
go install ...@latestwill behave, until we release an official new version we won't be able to check that.I also fixed
goreleaserconfig which was ONCE AGAIN misbehaving due to the recent changes they introduced. It should now not change the release's metadata, so If you mark it as pre-release or official version, it will keep it this way.