pypa/gh-action-pypi-publish (https://github.com/pypa/gh-action-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/
Configuration
📅 Schedule: Branch creation - "before 4am" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, 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.3->v1.11.0Release Notes
pypa/gh-action-pypi-publish (https://github.com/pypa/gh-action-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/Configuration
📅 Schedule: Branch creation - "before 4am" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.