Repository navigation
Validate and release with standard Go and GitHub tooling - #22
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.
CI installs Go from
go.mod, uses the normal module proxy, and checks tidiness, race tests, vet and formatting. A one-linego list -m allcheck keeps the server and SDK out of the protocol's module graph.The release workflow runs CI on
mainand validates the version format. It then creates the version tag at the validated commit through the GitHub API, which fails if the tag already exists, and publishes the release from that tag. This replaces the Python dependency-check and release-preflight scripts and their tests.