chore(deps): update pypa/gh-action-pypi-publish action to v1.12.2 #942
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/pypa-gh-action-pypi-publish-1.x
branch
from
111f1f0
to
49985cb
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/pypa-gh-action-pypi-publish-1.x
branch
from
49985cb
to
b3af882
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/pypa-gh-action-pypi-publish-1.x
branch
from
b3af882
to
1e60d97
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/pypa-gh-action-pypi-publish-1.x
branch
from
1e60d97
to
892c875
Compare
AndreMiras
approved these changes
Nov 7, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.10.2->v1.12.2Release Notes
pypa/gh-action-pypi-publish (pypa/gh-action-pypi-publish)
v1.12.2Compare Source
🐛 What's Fixed
The fix for signing legacy zip sdists turned out to be incomplete, so @woodruffw💰 promptly produced another follow-up that updated
pypi-attestationsfrom v0.0.13 to v0.0.15 in #297. This is the only change since the previous release.🪞 Full Diff: pypa/gh-action-pypi-publish@v1.12.1...v1.12.2
🧔♂️ Release Manager: @webknjaz 🇺🇦
v1.12.1Compare Source
v1.12.0Compare Source
⚡️ 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) 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.
🪞 Full Diff: pypa/gh-action-pypi-publish@v1.11.0...v1.12.0
🧔♂️ Release Manager: @webknjaz 🇺🇦
v1.11.0Compare Source
🔏 Helping you become a trusted supply chain link 🔗
Two months ago, in v1.10.0, @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”. 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💰 flipped the respective toggle in #277 with the possibility to opt-out.
🛠️ Internal Dependencies
@woodruffw💰 bumped
sigstoreto v3.5.1 andpypi-attestationsto v0.0.13 in lock files via #276.🪞 Full Diff: pypa/gh-action-pypi-publish@v1.10.3...v1.11.0
🧔♂️ Release Manager: @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/15871.
v1.10.3Compare Source
💅 Cosmetic Output Improvements
In #270, @facutuesca💰 made a follow-up to their previous PR #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💰 updated a few internal linter versions in #266, #267, and #271, no user impact. This is usually automated otherwise.
💪 New Contributors
🪞 Full Diff: pypa/gh-action-pypi-publish@v1.10.2...v1.10.3
🧔♂️ Release Manager: @webknjaz 🇺🇦
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.