Repository navigation
CIP-0008: record twine 6.1 Trusted Publishing - #1258
Merged
Merged
Conversation
lawrennd
commented
Nov 1, 2026
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1258 +/- ##
=======================================
Coverage 55.13% 55.13%
=======================================
Files 213 213
Lines 22580 22580
Branches 2666 2666
=======================================
Hits 12449 12449
Misses 9548 9548
Partials 583 583
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
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
id-token: write). TheTWINE_*lines left ind6bbf9f; v1.15.0 already minted a PyPI token that way (Discussion #1228).twine upload. Switching topypa/gh-action-pypi-publishis optional and only needed if we want PEP 740 attestations.releaseenvironment to the deploy job, then name that environment on the PyPI trusted publisher (workflow first).Test plan
cip/cip0008.md