gh-action-pypi-publish

💅 Cosmetic Output Improvements

In #270, @facutuesca💰 made a follow-up to their previous PR #250, making the hints show up more granularly. This effectively makes sure that the suggestion to enable Trusted Publishing does not get displayed when it's already in use. It also makes the message nicer in a few places on the UI.

🛠️ Internal Dependencies

@mosfet80💰 updated a few internal linter versions in #266, #267, and #271, no user impact. This is usually automated otherwise.

💪 New Contributors

• @mosfet80 made their first contribution in https://github.com/pypa/gh-action-pypi-publish/pull/266

🪞 Full Diff: https://github.com/pypa/gh-action-pypi-publish/compare/v1.10.2...v1.10.3

🧔‍♂️ Release Manager: @webknjaz 🇺🇦

💅 Cosmetic Output Improvements

In #250 and #258, @facutuesca💰 added a nudge message with a magic link to pre-fill the creation of new Trusted Publishers configurations on PyPI. The users are now suggested to configure tokenless publishing by clicking a link printed in the job summary when it's detected that they publish to PyPI or TestPyPI. Just like magic! 🦄

🛠️ Internal Dependencies

@woodruffw💰 bumped pypi-attestations to v0.0.12 in #262, hopefully fixing #263. 🤞 Nah.. that wasn't it.

[!TIP]
Please keep in mind that reusable workflows are not yet supported, even though they sometimes work, mostly by accident.

💪 New Contributors

@facutuesca made their first contribution in https://github.com/pypa/gh-action-pypi-publish/pull/258

🪞 Full Diff: https://github.com/pypa/gh-action-pypi-publish/compare/v1.10.1...v1.10.2

🧔‍♂️ Release Manager: @webknjaz 🇺🇦

🙏 Special Thanks to @henryiii💰 for promptly pointing up possible fixes for #263.

🚑🔏 Oopsie... We missed a tiny bug in the attestations feature the other day

The problem was that the distribution file validity check was failing on any valid distribution being present and ready to be signed. What a silly mistake! It's now been fixed via https://github.com/pypa/gh-action-pypi-publish/commit/0ab0b79, though. So everything's good!

-- @webknjaz💰

[!IMPORTANT]
✨ Despite this minor hiccup, we invite you to still opt into trying this feature out early. It can be enabled like this:

  with:
    attestations: true

Leave feedback in the v1.10.0 release discussion or the PR.

🪞 Full Diff: https://github.com/pypa/gh-action-pypi-publish/compare/v1.10.0...v1.10.1

🧔‍♂️ Release Manager: @webknjaz 🇺🇦

🙏 Special Thanks to @hugovk💰 for promptly validating the bug fix, mere minutes after I pushed it — I even haven't finished writing this text by then!

🔏 Anything fancy, eh?

This time, @woodruffw💰 implemented support for PEP 740 attestations functionality in #236 and #245. This is a big deal, as it is a huge step forward to replacing what the deprecated GPG signatures used to provide in a more meaningful way.

🙏 Please, thank William for working on this amazing improvement for the ecosystem! The overall effort is tracked @ https://github.com/pypi/warehouse/issues/15871, by the way.

🪞 Full Diff: https://github.com/pypa/gh-action-pypi-publish/compare/v1.9.0...v1.10.0

🧔‍♂️ Release Manager: @webknjaz 🇺🇦

💅 Cosmetic Output Improvements

• @woodruffw💰 updated the tense on password nudge in #234
• @shenxianpeng💰 helped us disable the progress bar that was being produced by the twine upload command via #231
• @woodruffw💰 also linked the PyPI status dashboard in the trusted publishing error message via https://github.com/pypa/gh-action-pypi-publish/pull/243

🛠️ Internal Dependencies

• pre-commit linters got auto-updated @ #225
• some notable dependency bumps include
  • cryptography == 42.0.7
  • id == 1.4.0
  • idna == 3.7 via #228
  • requests == 2.32.0 via #240
  • Twine == 5.1.0

⚙️ Secret Stuff

In #241, @br3ndonland💰 added a Docker label linking the container image to this repository for GHCR to display it nicely. This is preparatory work for a big performance-focused refactoring he's working on in #230.

💪 New Contributors

• @shenxianpeng made their first contribution in https://github.com/pypa/gh-action-pypi-publish/pull/231
• @br3ndonland made their first contribution in https://github.com/pypa/gh-action-pypi-publish/pull/241

🪞 Full Diff: https://github.com/pypa/gh-action-pypi-publish/compare/v1.8.14...v1.9.0

🧔‍♂️ Release Manager: @webknjaz 🇺🇦

🙏 Special Thanks to @pradyunsg💰 for promptly unblocking this release to Marketplace as GitHub started asking for yet another developer agreement signature from the organization admins.

🛠️ Internal Dependencies

Nothing changed feature-wise. The only notable update is that the underlying container runtime now uses Python 3.12 and pip has been updated to v24.0 there.
This is should go unnoticed in terms of behavior. It's just a bit of maintenance burden to be done occasionally by @webknjaz💰.
Enjoy!

🪞 Full Diff: https://github.com/pypa/gh-action-pypi-publish/compare/v1.8.13...v1.8.14

🧔‍♂️ Release Manager: @webknjaz 🇺🇦

🐛 What's Fixed

This action is now able to consume and publish distribution packages with Metadata-Version: 2.3 embedded.

🛠️ Internal Dependencies

@SigureMo💰 sent us a bump of pkginfo version to version 1.10.0 in #219. It's a transitive dependency for us and is not an API-level change but upgrading it has a side effect of letting Twine recognize distribution packages declaring Metadata-Version: 2.3. In particular, it is known to affect distributions built with Maturin >= 1.5.0.

Following that, @webknjaz💰 upgraded other transitive and direct dependency pins, including, among others, the following notable bumps:

• cryptography == 42.0.5
• id == 1.3.0
• readme-renderer == 43.0
• Twine == 5.0.0

💪 New Contributors

@SigureMo made their first contribution in https://github.com/pypa/gh-action-pypi-publish/pull/219

🪞 Full Diff: https://github.com/pypa/gh-action-pypi-publish/compare/v1.8.12...v1.8.13

🧔‍♂️ Release Manager: @webknjaz 🇺🇦

💅 Cosmetic Output Improvements

@woodruffw💰 replaced the notice annotations with simplified debug messages related to authentication methanism selection via #196. The also improved the error clarity during OIDC exchange on PRs from forks via #203.

📝 What's Documented

@virtuald💰 updated the docs and pointer messages were updated to mention that reusable workflows aren't supported right now in #186 and @xuanzhi33💰 later corrected the markdown syntax there via #216.

🛠️ Internal Dependencies

• pre-commit linters got autoupdated @ #204
• Cryptography was bumped from 41.0.6 to 42.0.4 @ #210, #213 and #214

⚙️ Secret Stuff

@woodruffw proactively updated the OIDC minting API endpoint used during the exchange via #206. Nothing you should be too concerned about, promise!

💪 New Contributors

• @virtuald made their first contribution in https://github.com/pypa/gh-action-pypi-publish/pull/186
• @xuanzhi33 made their first contribution in https://github.com/pypa/gh-action-pypi-publish/pull/216

🪞 Full Diff: https://github.com/pypa/gh-action-pypi-publish/compare/v1.8.11...v1.8.12

🧔‍♂️ Release Manager: @webknjaz 🇺🇦

💅 Cosmetic output improvements

@woodruffw added a nudge suggesting the users storing passwords in a GitHub Actions repository secrets to switch to using secretless publishing in https://github.com/pypa/gh-action-pypi-publish/pull/190. This also reminds people that PyPI will start mandating two-factor authentication to perform uploads in 2024.

📝 What's Documented

@di linked the configuration docs for Trusted Publishing in README via https://github.com/pypa/gh-action-pypi-publish/pull/179.

🛠️ Internal dependencies

• Cryptography was bumped from 41.0.3 to 41.0.6 @ https://github.com/pypa/gh-action-pypi-publish/pull/194
• Pip was bumped from 22.3.1 to 23.3 @ https://github.com/pypa/gh-action-pypi-publish/pull/189
• pre-commit linters got autoupdated @ https://github.com/pypa/gh-action-pypi-publish/pull/184
• Urllib3 was bumped from 2.0.3 to 2.0.7 @ https://github.com/pypa/gh-action-pypi-publish/pull/183 and https://github.com/pypa/gh-action-pypi-publish/pull/185

💪 New Contributors

• @di made their first contribution in https://github.com/pypa/gh-action-pypi-publish/pull/179

🪞 Full Diff: https://github.com/pypa/gh-action-pypi-publish/compare/v1.8.10...v1.8.11

🐛 What's Fixed

@woodruffw fixed decoding OIDC claims in debug output on failure by applying correct padding to the encoded payload via https://github.com/pypa/gh-action-pypi-publish/pull/177.

Full Diff: https://github.com/pypa/gh-action-pypi-publish/compare/v1.8.9...v1.8.10

💅 Cosmetic output improvements

• @woodruffw added debug output to the trusted publishing OIDC exchange on failures in https://github.com/pypa/gh-action-pypi-publish/pull/174
• @woodruffw implemented Markdown semantic callouts in README via https://github.com/pypa/gh-action-pypi-publish/pull/175

🛠️ Internal dependencies

• Certifi was bumped from 2023.5.7 to 2023.7.22 @ https://github.com/pypa/gh-action-pypi-publish/pull/171
• Cryptography was bumped from 41.0.2 to 41.0.3 @ https://github.com/pypa/gh-action-pypi-publish/pull/172

Full Diff: https://github.com/pypa/gh-action-pypi-publish/compare/v1.8.8...v1.8.9

💅 Cosmetic output improvements

• In https://github.com/pypa/gh-action-pypi-publish/pull/167, @woodruffw introduced a nudge-warning encouraging people to start using secretless publishing to PyPI, as suggested by @sethmlarson in https://github.com/pypa/gh-action-pypi-publish/issues/164, collaborating with @di.

  💡 Tip: The OIDC-based trusted publishing integration details can be found in the action README at https://github.com/marketplace/actions/pypi-publish#trusted-publishing and on the PyPI docs page at https://docs.pypi.org/trusted-publishers/. It's gone GA on April 20, 2023, during PyCon: https://blog.pypi.org/posts/2023-04-20-introducing-trusted-publishers/. And the Trail Of Bits blog post has some deeper explanation here: https://blog.trailofbits.com/2023/05/23/trusted-publishing-a-new-benchmark-for-packaging-security/.

🛠️ Internal dependencies

• @pquentin bumped the runtime dependency pins to the recent versions @ https://github.com/pypa/gh-action-pypi-publish/pull/168.

💪 New Contributors

• @pquentin made their first contribution in https://github.com/pypa/gh-action-pypi-publish/pull/168

🪞 Full Diff: https://github.com/pypa/gh-action-pypi-publish/compare/v1.8.7...v1.8.8

💅 Cosmetic output impovements

• @woodruffw fixed OIDC the multiline annotations by escaping LF through urlencoding it in https://github.com/pypa/gh-action-pypi-publish/pull/156.
• @jaap3 noticed and promptly removed extraneous } from a non-OIDC log annotation in https://github.com/pypa/gh-action-pypi-publish/pull/161.
• @hugovk made pip ignore that it runs under the root user and suppress its warning output in https://github.com/pypa/gh-action-pypi-publish/pull/159.

🛠️ Internal dependencies

• Cryptography was bumped from 39.0.1 to 41.0.0 @ https://github.com/pypa/gh-action-pypi-publish/pull/160
• Requests was bumped from 2.28.1 to 2.31.0 @ https://github.com/pypa/gh-action-pypi-publish/pull/157

💪 New Contributors

• @jaap3 made their first contribution in https://github.com/pypa/gh-action-pypi-publish/pull/161

🪞 Full Diff: https://github.com/pypa/gh-action-pypi-publish/compare/v1.8.6...v1.8.7

What's Updated

• @woodruffw dropped the references to a “private beta” from the project docs and runtime in https://github.com/pypa/gh-action-pypi-publish/pull/147. He also clarified that the API tokens are still more secure than passwords in https://github.com/pypa/gh-action-pypi-publish/pull/150.
• @asherf noticed that the action metadata incorrectly marked the password field as required and contributed a correction in https://github.com/pypa/gh-action-pypi-publish/pull/151
• @webknjaz moved the Trusted Publishing example to the top of the README in hopes that new users would default to using it via https://github.com/pypa/gh-action-pypi-publish/commit/f47b34707fd264d5ddb1ef322ca74cf8e4cf351b

New Contributors

• @asherf made their first contribution in https://github.com/pypa/gh-action-pypi-publish/pull/151

Full Diff: https://github.com/pypa/gh-action-pypi-publish/compare/v1.8.5...v1.8.6

What's Improved

@woodruffw improved the user-facing documentation and logging to make use of the Trusted Publishing flow terminology cohesive with PyPI in https://github.com/pypa/gh-action-pypi-publish/pull/143. Trusted Publishing used to be referred to as OpenID Connect (OIDC) — the underlying technology that is being used to make it work. He also made the action display the cause of the Trusted Publishing flow being selected by the action via https://github.com/pypa/gh-action-pypi-publish/pull/142.

Full Diff: https://github.com/pypa/gh-action-pypi-publish/compare/v1.8.4...v1.8.5

What's Improved

• @hugovk cleaned up the double whitespaces in the OIDC flow logging in https://github.com/pypa/gh-action-pypi-publish/pull/140
• @woodruffw added a title and a docs link to the OIDC error output in https://github.com/pypa/gh-action-pypi-publish/pull/139

Full Diff: https://github.com/pypa/gh-action-pypi-publish/compare/v1.8.3...v1.8.4

What's New

This release improves the logging detalization of which authentication mode is selected when the action runs. It surfaces this detail to the workflow run summary page as annotations. The change was contributed by @woodruffw in https://github.com/pypa/gh-action-pypi-publish/pull/136.

Full Diff: https://github.com/pypa/gh-action-pypi-publish/compare/v1.8.2...v1.8.3

What's Changed

This release started printing out full OIDC error messages to console, instead of just one line -- by @woodruffw in https://github.com/pypa/gh-action-pypi-publish/pull/134.

Full Diff: https://github.com/pypa/gh-action-pypi-publish/compare/v1.8.1...v1.8.2

🐛 What's Fixed

💔 Unfortunately, a tiny mistake in v1.8.0 caused a far-reaching regression for the most used code path.
❗ But don't worry, it's fixed now thanks to @njzjz who promptly spotted it and @zhongjiajie who sent a bugfix.

🙌 New Contributors

• @zhongjiajie made their first contribution in https://github.com/pypa/gh-action-pypi-publish/pull/131

Full Diff: https://github.com/pypa/gh-action-pypi-publish/compare/v1.8.0...v1.8.1

The Coolest Release Ever!

In this release, @woodruffw implemented support for secretless OIDC-based publishing to PyPI-like package indexes. The OIDC flow is activated when neither username nor password action inputs are set.

The OIDC “token exchange”, is an authentication technique that PyPI (and TestPyPI, and hopefully some future others) supports as an alternative to long-lived username/password combinations or long-lived API tokens.

IMPORTANT: The PyPI-side configuration is only available to participants of the private beta test. Please, only try out the zero-config mode if you are a beta test participant having followed the PyPI configuration instructions.
It's gone GA during Python 2023 and is available to everyone now.

Setup prerequisites: https://github.com/marketplace/actions/pypi-publish#trusted-publishing
PyPI's documentation: https://pypi.org/help/#trusted-publishers
Beta test enrollment: https://github.com/pypi/warehouse/issues/12965

New Contributors

• @woodruffw made their first contribution in https://github.com/pypa/gh-action-pypi-publish/pull/123

Full Diff: https://github.com/pypa/gh-action-pypi-publish/compare/v1.7.1...v1.8.0