pypa/gh-action-pypi-publish (pypa/gh-action-pypi-publish)
### [`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
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.11.0
->v1.12.0
Release Notes
pypa/gh-action-pypi-publish (pypa/gh-action-pypi-publish)
### [`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-publishConfiguration
📅 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.