pypa/gh-action-pypi-publish (pypa/gh-action-pypi-publish)
### [`v1.12.2`](https://redirect.github.com/pypa/gh-action-pypi-publish/releases/tag/v1.12.2)
[Compare Source](https://redirect.github.com/pypa/gh-action-pypi-publish/compare/v1.12.1...v1.12.2)
#### 🐛 What's Fixed
The fix for signing legacy zip sdists turned out to be incomplete, so [@woodruffw](https://redirect.github.com/woodruffw)[💰](https://redirect.github.com/sponsors/woodruffw) promptly produced another follow-up that updated `pypi-attestations` from v0.0.13 to v0.0.15 in [#297](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/297). This is the only change since the previous release.
**🪞 Full Diff**: https://github.com/pypa/gh-action-pypi-publish/compare/v1.12.1...v1.12.2
**🧔♂️ Release Manager:** [@webknjaz](https://redirect.github.com/sponsors/webknjaz) [🇺🇦](https://stand-with-ukraine.pp.ua)
### [`v1.12.1`](https://redirect.github.com/pypa/gh-action-pypi-publish/compare/v1.12.0...v1.12.1)
[Compare Source](https://redirect.github.com/pypa/gh-action-pypi-publish/compare/v1.12.0...v1.12.1)
### [`v1.12.0`](https://redirect.github.com/pypa/gh-action-pypi-publish/releases/tag/v1.12.0)
[Compare Source](https://redirect.github.com/pypa/gh-action-pypi-publish/compare/v1.11.0...v1.12.0)
##### ⚡️ Why Should You Update?
This is a minor version bump, but it does not add any new user-facing interfaces. Still, I felt like it should not be a patch-release: this update brings *significant changes* to the action invocation and internal release process.
Previously, each invocation of [`pypi-publish`][pypi-publish] required building a container image in the invoking CI job. This was inefficient and added about 30 seconds to the publishing jobs at their startup just to build the container.
I wanted to improve this for over three years ([#58](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/58)) and a little over half a year ago [@br3ndonland](https://redirect.github.com/br3ndonland)[💰](https://redirect.github.com/sponsors/br3ndonland) stepped up and offered a very comprehensive solution to the limitation I was hoping to overcome: [#230](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/230).
Going forward, I'm going to pre-build per-version containers prior to cutting each release. And the action invocations will just pull the image from GitHub Container registry.
**🪞 Full Diff**: https://github.com/pypa/gh-action-pypi-publish/compare/v1.11.0...v1.12.0
**🧔♂️ Release Manager:** [@webknjaz 🇺🇦](https://redirect.github.com/sponsors/webknjaz)
[`pypi-publish`]: https://redirect.github.com/marketplace/actions/pypi-publish
### [`v1.11.0`](https://redirect.github.com/pypa/gh-action-pypi-publish/releases/tag/v1.11.0)
[Compare Source](https://redirect.github.com/pypa/gh-action-pypi-publish/compare/v1.10.3...v1.11.0)
#### 🔏 Helping you become a trusted supply chain link 🔗
Two months ago, in [v1.10.0](https://redirect.github.com/pypa/gh-action-pypi-publish/releases/tag/v1.10.0), [@woodruffw](https://redirect.github.com/woodruffw)[💰](https://redirect.github.com/sponsors/woodruffw) integrated support for generating and uploading [PEP 740] digital attestations that can be used as provenance objects when analyzing dependency chains for the integrity.
To make sure it works well, it was implemented as an opt-in, so a relatively small subset of projects was able to try it out, and a few issues have been determined and fixed during this time.
That changes today! This version changes the feature toggle to [“on by default”](https://redirect.github.com/marketplace/actions/pypi-publish#generating-and-uploading-attestations). This means that from now on, every project making use of Trusted Publishing will start producing and publishing digital attestations without having to do any modifications to how they use this action.
[@woodruffw](https://redirect.github.com/woodruffw)[💰](https://redirect.github.com/sponsors/woodruffw) flipped the respective toggle in [#277](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/277) with the possibility to opt-out.
#### 🛠️ Internal Dependencies
[@woodruffw](https://redirect.github.com/woodruffw)[💰](https://redirect.github.com/sponsors/woodruffw) bumped `sigstore` to v3.5.1 and `pypi-attestations` to v0.0.13 in lock files via [#276](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/276).
**🪞 Full Diff**: https://github.com/pypa/gh-action-pypi-publish/compare/v1.10.3...v1.11.0
**🧔♂️ Release Manager:** [@webknjaz 🇺🇦](https://redirect.github.com/sponsors/webknjaz)
**🙏 Special Thanks** to William for working on improving the supply chain provenance in the ecosystem! The overall effort is tracked @&#[https://github.com/pypi/warehouse/issues/15871](https://redirect.github.com/pypi/warehouse/issues/15871)/15871.
[PEP 740]: https://peps.python.org/pep-0740/
### [`v1.10.3`](https://redirect.github.com/pypa/gh-action-pypi-publish/releases/tag/v1.10.3)
[Compare Source](https://redirect.github.com/pypa/gh-action-pypi-publish/compare/v1.10.2...v1.10.3)
#### 💅 Cosmetic Output Improvements
In [#270](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/270), [@facutuesca](https://redirect.github.com/facutuesca)[💰](https://redirect.github.com/sponsors/facutuesca) made a follow-up to their previous PR [#250](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/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](https://redirect.github.com/mosfet80)[💰](https://redirect.github.com/sponsors/mosfet80) updated a few internal linter versions in [#266](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/266), [#267](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/267), and [#271](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/271), no user impact. This is usually automated otherwise.
#### 💪 New Contributors
- [@mosfet80](https://redirect.github.com/mosfet80) made their first contribution in [https://github.com/pypa/gh-action-pypi-publish/pull/266](https://redirect.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 🇺🇦](https://redirect.github.com/sponsors/webknjaz)
### [`v1.10.2`](https://redirect.github.com/pypa/gh-action-pypi-publish/releases/tag/v1.10.2)
[Compare Source](https://redirect.github.com/pypa/gh-action-pypi-publish/compare/v1.10.1...v1.10.2)
#### 💅 Cosmetic Output Improvements
In [#250](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/250) and [#258](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/258), [@facutuesca](https://redirect.github.com/facutuesca)[💰](https://redirect.github.com/sponsors/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](https://redirect.github.com/woodruffw)[💰](https://redirect.github.com/sponsors/woodruffw) bumped `pypi-attestations` to v0.0.12 in [#262](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/262), ~hopefully fixing [#263](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/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](https://redirect.github.com/facutuesca) made their first contribution in [https://github.com/pypa/gh-action-pypi-publish/pull/258](https://redirect.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 🇺🇦](https://redirect.github.com/sponsors/webknjaz)
**🙏 Special Thanks** to [@henryiii](https://redirect.github.com/henryiii)[💰](https://redirect.github.com/sponsors/henryiii) for promptly pointing up possible fixes for [#263](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/263).
### [`v1.10.1`](https://redirect.github.com/pypa/gh-action-pypi-publish/releases/tag/v1.10.1)
[Compare Source](https://redirect.github.com/pypa/gh-action-pypi-publish/compare/v1.10.0...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 https://github.com/pypa/gh-action-pypi-publish/commit/0ab0b79, though. So everything's good!
\-- [@webknjaz](https://redirect.github.com/webknjaz)[💰](https://redirect.github.com/sponsors/webknjaz)
> \[!IMPORTANT]
> ✨ Despite this minor hiccup, we invite you to still opt into trying this feature out early. [It can be enabled](https://redirect.github.com/marketplace/actions/pypi-publish#generating-and-uploading-attestations) like this:
>
> ```yml
> with:
> attestations: true
> ```
>
> Leave feedback in [the v1.10.0 release discussion](https://redirect.github.com/pypa/gh-action-pypi-publish/discussions/255) or [the PR](https://redirect.github.com/pypa/gh-action-pypi-publish/pull/236).
**🪞 Full Diff**: https://github.com/pypa/gh-action-pypi-publish/compare/v1.10.0...v1.10.1
**🧔♂️ Release Manager:** [@webknjaz 🇺🇦](https://redirect.github.com/sponsors/webknjaz)
**🙏 Special Thanks** to [@hugovk](https://redirect.github.com/hugovk)[💰](https://redirect.github.com/sponsors/hugovk) for [promptly validating the bug fix](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/256#issuecomment-2325925847), mere minutes after I pushed it — I even haven't finished writing this text by then!
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
[ ] If you want to rebase/retry this PR, check this box
This PR contains the following updates:
v1.10.0->v1.12.2Release Notes
pypa/gh-action-pypi-publish (pypa/gh-action-pypi-publish)
### [`v1.12.2`](https://redirect.github.com/pypa/gh-action-pypi-publish/releases/tag/v1.12.2) [Compare Source](https://redirect.github.com/pypa/gh-action-pypi-publish/compare/v1.12.1...v1.12.2) #### 🐛 What's Fixed The fix for signing legacy zip sdists turned out to be incomplete, so [@woodruffw](https://redirect.github.com/woodruffw)[💰](https://redirect.github.com/sponsors/woodruffw) promptly produced another follow-up that updated `pypi-attestations` from v0.0.13 to v0.0.15 in [#297](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/297). This is the only change since the previous release. **🪞 Full Diff**: https://github.com/pypa/gh-action-pypi-publish/compare/v1.12.1...v1.12.2 **🧔♂️ Release Manager:** [@webknjaz](https://redirect.github.com/sponsors/webknjaz) [🇺🇦](https://stand-with-ukraine.pp.ua) ### [`v1.12.1`](https://redirect.github.com/pypa/gh-action-pypi-publish/compare/v1.12.0...v1.12.1) [Compare Source](https://redirect.github.com/pypa/gh-action-pypi-publish/compare/v1.12.0...v1.12.1) ### [`v1.12.0`](https://redirect.github.com/pypa/gh-action-pypi-publish/releases/tag/v1.12.0) [Compare Source](https://redirect.github.com/pypa/gh-action-pypi-publish/compare/v1.11.0...v1.12.0) ##### ⚡️ Why Should You Update? This is a minor version bump, but it does not add any new user-facing interfaces. Still, I felt like it should not be a patch-release: this update brings *significant changes* to the action invocation and internal release process. Previously, each invocation of [`pypi-publish`][pypi-publish] required building a container image in the invoking CI job. This was inefficient and added about 30 seconds to the publishing jobs at their startup just to build the container. I wanted to improve this for over three years ([#58](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/58)) and a little over half a year ago [@br3ndonland](https://redirect.github.com/br3ndonland)[💰](https://redirect.github.com/sponsors/br3ndonland) stepped up and offered a very comprehensive solution to the limitation I was hoping to overcome: [#230](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/230). Going forward, I'm going to pre-build per-version containers prior to cutting each release. And the action invocations will just pull the image from GitHub Container registry. **🪞 Full Diff**: https://github.com/pypa/gh-action-pypi-publish/compare/v1.11.0...v1.12.0 **🧔♂️ Release Manager:** [@webknjaz 🇺🇦](https://redirect.github.com/sponsors/webknjaz) [`pypi-publish`]: https://redirect.github.com/marketplace/actions/pypi-publish ### [`v1.11.0`](https://redirect.github.com/pypa/gh-action-pypi-publish/releases/tag/v1.11.0) [Compare Source](https://redirect.github.com/pypa/gh-action-pypi-publish/compare/v1.10.3...v1.11.0) #### 🔏 Helping you become a trusted supply chain link 🔗 Two months ago, in [v1.10.0](https://redirect.github.com/pypa/gh-action-pypi-publish/releases/tag/v1.10.0), [@woodruffw](https://redirect.github.com/woodruffw)[💰](https://redirect.github.com/sponsors/woodruffw) integrated support for generating and uploading [PEP 740] digital attestations that can be used as provenance objects when analyzing dependency chains for the integrity. To make sure it works well, it was implemented as an opt-in, so a relatively small subset of projects was able to try it out, and a few issues have been determined and fixed during this time. That changes today! This version changes the feature toggle to [“on by default”](https://redirect.github.com/marketplace/actions/pypi-publish#generating-and-uploading-attestations). This means that from now on, every project making use of Trusted Publishing will start producing and publishing digital attestations without having to do any modifications to how they use this action. [@woodruffw](https://redirect.github.com/woodruffw)[💰](https://redirect.github.com/sponsors/woodruffw) flipped the respective toggle in [#277](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/277) with the possibility to opt-out. #### 🛠️ Internal Dependencies [@woodruffw](https://redirect.github.com/woodruffw)[💰](https://redirect.github.com/sponsors/woodruffw) bumped `sigstore` to v3.5.1 and `pypi-attestations` to v0.0.13 in lock files via [#276](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/276). **🪞 Full Diff**: https://github.com/pypa/gh-action-pypi-publish/compare/v1.10.3...v1.11.0 **🧔♂️ Release Manager:** [@webknjaz 🇺🇦](https://redirect.github.com/sponsors/webknjaz) **🙏 Special Thanks** to William for working on improving the supply chain provenance in the ecosystem! The overall effort is tracked @&#[https://github.com/pypi/warehouse/issues/15871](https://redirect.github.com/pypi/warehouse/issues/15871)/15871. [PEP 740]: https://peps.python.org/pep-0740/ ### [`v1.10.3`](https://redirect.github.com/pypa/gh-action-pypi-publish/releases/tag/v1.10.3) [Compare Source](https://redirect.github.com/pypa/gh-action-pypi-publish/compare/v1.10.2...v1.10.3) #### 💅 Cosmetic Output Improvements In [#270](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/270), [@facutuesca](https://redirect.github.com/facutuesca)[💰](https://redirect.github.com/sponsors/facutuesca) made a follow-up to their previous PR [#250](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/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](https://redirect.github.com/mosfet80)[💰](https://redirect.github.com/sponsors/mosfet80) updated a few internal linter versions in [#266](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/266), [#267](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/267), and [#271](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/271), no user impact. This is usually automated otherwise. #### 💪 New Contributors - [@mosfet80](https://redirect.github.com/mosfet80) made their first contribution in [https://github.com/pypa/gh-action-pypi-publish/pull/266](https://redirect.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 🇺🇦](https://redirect.github.com/sponsors/webknjaz) ### [`v1.10.2`](https://redirect.github.com/pypa/gh-action-pypi-publish/releases/tag/v1.10.2) [Compare Source](https://redirect.github.com/pypa/gh-action-pypi-publish/compare/v1.10.1...v1.10.2) #### 💅 Cosmetic Output Improvements In [#250](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/250) and [#258](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/258), [@facutuesca](https://redirect.github.com/facutuesca)[💰](https://redirect.github.com/sponsors/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](https://redirect.github.com/woodruffw)[💰](https://redirect.github.com/sponsors/woodruffw) bumped `pypi-attestations` to v0.0.12 in [#262](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/262), ~hopefully fixing [#263](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/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](https://redirect.github.com/facutuesca) made their first contribution in [https://github.com/pypa/gh-action-pypi-publish/pull/258](https://redirect.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 🇺🇦](https://redirect.github.com/sponsors/webknjaz) **🙏 Special Thanks** to [@henryiii](https://redirect.github.com/henryiii)[💰](https://redirect.github.com/sponsors/henryiii) for promptly pointing up possible fixes for [#263](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/263). ### [`v1.10.1`](https://redirect.github.com/pypa/gh-action-pypi-publish/releases/tag/v1.10.1) [Compare Source](https://redirect.github.com/pypa/gh-action-pypi-publish/compare/v1.10.0...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 https://github.com/pypa/gh-action-pypi-publish/commit/0ab0b79, though. So everything's good! \-- [@webknjaz](https://redirect.github.com/webknjaz)[💰](https://redirect.github.com/sponsors/webknjaz) > \[!IMPORTANT] > ✨ Despite this minor hiccup, we invite you to still opt into trying this feature out early. [It can be enabled](https://redirect.github.com/marketplace/actions/pypi-publish#generating-and-uploading-attestations) like this: > > ```yml > with: > attestations: true > ``` > > Leave feedback in [the v1.10.0 release discussion](https://redirect.github.com/pypa/gh-action-pypi-publish/discussions/255) or [the PR](https://redirect.github.com/pypa/gh-action-pypi-publish/pull/236). **🪞 Full Diff**: https://github.com/pypa/gh-action-pypi-publish/compare/v1.10.0...v1.10.1 **🧔♂️ Release Manager:** [@webknjaz 🇺🇦](https://redirect.github.com/sponsors/webknjaz) **🙏 Special Thanks** to [@hugovk](https://redirect.github.com/hugovk)[💰](https://redirect.github.com/sponsors/hugovk) for [promptly validating the bug fix](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/256#issuecomment-2325925847), mere minutes after I pushed it — I even haven't finished writing this text by then!Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.