Releases: pypa/gh-action-pypi-publish
v1.10.1
🚑🔏 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 0ab0b79, though. So everything's good!
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: trueLeave feedback in the v1.10.0 release discussion or the PR.
🪞 Full Diff: 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!
Contributors
Assets 2
v1.10.0
🔏 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.
Important
✨ Please, do opt into trying this feature out early. It can be enabled as follows:
with:
attestations: trueLeave any feedback on this in this release discussion or the PR.
🙏 And please, thank William for working on this amazing improvement for the ecosystem! The overall effort is tracked @ pypi/warehouse#15871, by the way.
🪞 Full Diff: v1.9.0...v1.10.0
🧔♂️ Release Manager: @webknjaz 🇺🇦
v1.9.0
💅 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 uploadcommand via #231 - @woodruffw💰 also linked the PyPI status dashboard in the trusted publishing error message via #243
🛠️ Internal Dependencies
- pre-commit linters got auto-updated @ #225
- some notable dependency bumps include
⚙️ 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 #231
- @br3ndonland made their first contribution in #241
🪞 Full Diff: 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.
v1.8.14
🛠️ 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: v1.8.13...v1.8.14
🧔♂️ Release Manager: @webknjaz 🇺🇦
v1.8.13
🐛 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.5id == 1.3.0readme-renderer == 43.0Twine == 5.0.0
💪 New Contributors
@SigureMo made their first contribution in #219
🪞 Full Diff: v1.8.12...v1.8.13
🧔♂️ Release Manager: @webknjaz 🇺🇦
v1.8.12
💅 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 #186
- @xuanzhi33 made their first contribution in #216
🪞 Full Diff: v1.8.11...v1.8.12
🧔♂️ Release Manager: @webknjaz 🇺🇦
v1.8.11
💅 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 #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 #179.
🛠️ Internal dependencies
- Cryptography was bumped from 41.0.3 to 41.0.6 @ #194
- Pip was bumped from 22.3.1 to 23.3 @ #189
- pre-commit linters got autoupdated @ #184
- Urllib3 was bumped from 2.0.3 to 2.0.7 @ #183 and #185
💪 New Contributors
🪞 Full Diff: v1.8.10...v1.8.11
v1.8.10
🐛 What's Fixed
@woodruffw fixed decoding OIDC claims in debug output on failure by applying correct padding to the encoded payload via #177.
Full Diff: v1.8.9...v1.8.10
v1.8.9
💅 Cosmetic output improvements
- @woodruffw added debug output to the trusted publishing OIDC exchange on failures in #174
- @woodruffw implemented Markdown semantic callouts in README via #175
🛠️ Internal dependencies
- Certifi was bumped from 2023.5.7 to 2023.7.22 @ #171
- Cryptography was bumped from 41.0.2 to 41.0.3 @ #172
Full Diff: v1.8.8...v1.8.9
v1.8.8
💅 Cosmetic output improvements
-
In #167, @woodruffw introduced a nudge-warning encouraging people to start using secretless publishing to PyPI, as suggested by @sethmlarson in #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
💪 New Contributors
🪞 Full Diff: v1.8.7...v1.8.8
