ci: enable GitHub releases on tag push - #19
Merged
Merged
Conversation
Goreleaser now creates a GitHub release with binaries, checksums, and GPG signatures attached. S3 upload continues as before. - .goreleaser.yaml: replace disable:true with draft:false, prerelease:auto - release.yml: drop --skip=publish, upgrade to contents:write
Resolves the latest v* tag at dispatch time instead of triggering on tag push. Goreleaser and S3 upload both use the resolved tag.
Runs in parallel with the binary release job. Uses OIDC auth, updates server.json version from the resolved tag.
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
1 participant
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
prerelease: automarks tags likev1.0.0-rc1as pre-releases automaticallyChanges
.goreleaser.yaml:release.disable: truereplaced withdraft: false, prerelease: autorelease.yml: dropped--skip=publish, upgraded top-level permission tocontents: writeNote
Merge #18 (MCP registry publish) first or after; both touch
release.ymlpermissions. If #18 merges first, this PR needs a rebase to reconcilecontents: writewithid-token: write(both are needed).