Sourced from pypa/gh-action-pypi-publish's releases.
v1.12.2
🐛 What's Fixed
The fix for signing legacy zip sdists turned out to be incomplete, so
@woodruffw
💰 promptly produced another follow-up that updatedpypi-attestations
from v0.0.13 to v0.0.15 in #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
🇺🇦v1.12.1
🐛 What's Fixed
Version v1.12.0 hit several rare corner cases we never considered fully supported, and this release fixes a few of those. In #294,
@webknjaz
💰 improved the self-hosted runner experience by pre-installing Python if it's not there, and with #293 the ability to use the action on GitHub Enterprise instances has been restored. The latter should've also fixed the ability to invokepypi-publish
from nested in-repo composite actions — another exotic use-case that was never tested in our CI.@woodruffw
💰 also managed to squeeze in a last-minute fix for detecting legacy.zip
sdists while producing attestations via #295.🪞 Full Diff: https://github.com/pypa/gh-action-pypi-publish/compare/v1.12.0...v1.12.1
🧔♂️ Release Manager:
@webknjaz
🇺🇦🙏 Huge Thanks to all the bug reporters for posting the logs, helping inspect the problems and verify the regression fixes!
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
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) and a little over half a year ago
@br3ndonland
💰 stepped up and offered a very comprehensive solution to the limitation I was hoping to overcome: #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.
[!CAUTION] Known quirks:
- This seems to not work on self-hosted runners without a
python
executable: #289. The workaround could be installing it prior to running the action.Pinning to commit hashes does not work: #290. Workaround: postpone updating until it's fixed or switch to Git tags for now. Subscribe to that issue to follow the progress.UPD: This was an issue during the first 12 hours post release and it has been addressed upstream by publishing a commit SHA-tagged image for the release on Nov 12, 2024 at 10:27 UTC+1.- Calling
pypi-publish
from another nested repo-local composite action might be breaking file paths: #291. Workaround: postpone updating until it's fixed. Subscribe to that issue to follow the progress.- Running within GitHub Enterprise fails on the action repo clone: #292. Workaround: postpone updating until it's fixed. Subscribe to that issue to follow the progress.
🪞 Full Diff: https://github.com/pypa/gh-action-pypi-publish/compare/v1.11.0...v1.12.0
🧔♂️ Release Manager:
@webknjaz 🇺🇦
15c56db
Merge pull request #297
from trail-of-forks/ww/bump-pypi-attestationsfe8d148
requirements: bump pypi-attestations to 0.0.151f5d4ec
Merge pull request #295
from trail-of-forks/ww/fix-sdist-collectionfec2f0c
attestations: collect *.zip sdists as wella8b73a6
Merge pull request #294
from webknjaz/bugfixes/optional-python9b4dfb0
✨ Pre-install Python if there's none0a87186
Merge pull request #293
from webknjaz/bugfixes/uncheckout-intermediate-actiondfcfeca
🧪 Use prefetched action to make trampoline0d02f37
📝💅 Update the CI/CD badge in README61da13d
Merge pull request #230
from br3ndonland/ghcr