fix(ci): authenticate release pushes explicitly - #130
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #130 +/- ##
=======================================
Coverage 97.74% 97.74%
=======================================
Files 1 1
Lines 133 133
Branches 7 7
=======================================
Hits 130 130
Misses 3 3
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. |
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.
Problem\n\n- The stored release PAT cannot authenticate through checkout’s raw-token input.\n- Release preparation stops before the protected-main promotion begins.\n\n# Solution\n\n- Use the standard GitHub token for checkout.\n- Remove persisted checkout credentials before release pushes.\n- Match Python Semantic Release’s proven actor-token HTTPS authentication.\n- Apply the PAT only to explicit release pushes.\n- Preserve tested-SHA promotion and the protected-main ruleset.\n\nfs-3z4