Repository navigation
chore: 版本号提升到 v0.3.0(发版前置步骤) - #31
Merged
Merged
Conversation
发版流程修正:二进制版本来自 go:embed .version/VERSION(main.go SetVersion), 打 tag 前必须先更新并合并该文件,再创建 tag 触发 goreleaser。
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.
修复发版流程:
protobuild version读的是 go:embed 的.version/VERSION,此前 v0.3.0 tag 打在了未更新 VERSION 的提交上,导致产物内嵌版本号仍是 v0.2.1。.version/VERSION更新为 v0.3.0