{{ message }}
Repository navigation
ci: use release PAT for protected tags - #1419
Merged
Merged
Conversation
Signed-off-by: Ricky-7-Yan <2314530442@qq.com>
Ricky-7-Yan
requested review from
TerryHowe,
Wwwsylvia,
sabre1041 and
shizhMSFT
as code owners
September 11, 2026 16:25
Member
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.
Summary
RELEASE_PATrepository secret in the main-branch release checkoutGITHUB_TOKENThis mirrors the already merged v2 fix in #1371.
Verification
.github/workflows/release.ymlremains LF-onlygit diff --checkpassedgo test ./...was attempted with Go 1.26; unrelated Windows-only baseline failures remain around symlink privilege, Unix file modes, XDG paths, andfile://C:\...URL handlingThe protected tag push can only be verified by the next repository release workflow.
Fixes #1411