Repository navigation
ci: require validation of tagged commits before publishing - #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.
A tag-only push could publish a release without testing the tagged commit. The release workflow now requires successful tests on Linux, macOS, and Windows plus golangci-lint before GoReleaser runs. All jobs check out the same event SHA.
The workflow defaults to read-only repository permissions; only the publication job receives contents:write.
Closes #12
Validation: actionlint v1.7.7 passes. Checked the validation dependencies, matching checkout SHAs, platform matrix, and job permissions. Publication itself is not run during this PR.