Update pypa/gh-action-pypi-publish action to v1.12.3 #20
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
5f850d8 to
0cc1ac2
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #20 +/- ##
=======================================
Coverage 82.75% 82.75%
=======================================
Files 4 4
Lines 174 174
=======================================
Hits 144 144
Misses 30 30 |
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/pypa-gh-action-pypi-publish-1.x
branch
from
0cc1ac2 to
1102163
Compare
renovate
bot
force-pushed
the
renovate/pypa-gh-action-pypi-publish-1.x
branch
from
1102163 to
c2c2bfd
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/pypa-gh-action-pypi-publish-1.x
branch
from
c2c2bfd to
a060370
Compare
renovate
bot
changed the title
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?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
a060370 to
3e01385
Compare
renovate
bot
force-pushed
the
renovate/pypa-gh-action-pypi-publish-1.x
branch
from
3e01385 to
7195994
Compare
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/pypa-gh-action-pypi-publish-1.x
branch
from
7195994 to
5d07932
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/pypa-gh-action-pypi-publish-1.x
branch
from
5d07932 to
926091c
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/pypa-gh-action-pypi-publish-1.x
branch
from
926091c to
5104e6b
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/pypa-gh-action-pypi-publish-1.x
branch
from
5104e6b to
c3cf400
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/pypa-gh-action-pypi-publish-1.x
branch
from
c3cf400 to
6ff5742
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/pypa-gh-action-pypi-publish-1.x
branch
from
6ff5742 to
5ad42a7
Compare
| @@ -51,7 +51,7 @@ | |||
| sed -i "s/5 - Production\/Stable/4 - Beta/g" setup.py | |||
| python setup.py clean check sdist bdist_wheel | |||
| - name: Upload to PyPI Test | |||
| uses: pypa/gh-action-pypi-publish@v1.8.10 | |||
| uses: pypa/gh-action-pypi-publish@v1.12.3 | |||
Check warning
Code scanning / Semgrep (reported by Codacy)
An action sourced from a third-party repository on GitHub is not pinned to a full length commit SHA. Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Warning
| @@ -71,7 +71,7 @@ | |||
| pip install wheel -r requirements.txt | |||
| python setup.py clean check sdist bdist_wheel | |||
| - name: Upload to PyPI | |||
| uses: pypa/gh-action-pypi-publish@v1.8.10 | |||
| uses: pypa/gh-action-pypi-publish@v1.12.3 | |||
Check warning
Code scanning / Semgrep (reported by Codacy)
An action sourced from a third-party repository on GitHub is not pinned to a full length commit SHA. Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Warning
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.8.10->v1.12.3Release Notes
pypa/gh-action-pypi-publish (pypa/gh-action-pypi-publish)
v1.12.3Compare Source
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
🐛 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 invoke [
pypi-publish][pypi-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
.zipsdists while producing attestations via #295.🪞 Full Diff: pypa/gh-action-pypi-publish@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.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 🇺🇦
v1.10.2Compare Source
💅 Cosmetic Output Improvements
In #250 and #258, @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💰 bumped
pypi-attestationsto v0.0.12 in #262, fixing #263.💪 New Contributors
@facutuesca made their first contribution in https://github.com/pypa/gh-action-pypi-publish/pull/258
🪞 Full Diff: pypa/gh-action-pypi-publish@v1.10.1...v1.10.2
🧔♂️ Release Manager: @webknjaz 🇺🇦
🙏 Special Thanks to @henryiii💰 for promptly pointing up possible fixes for #263.
v1.10.1Compare Source
🚑🔏 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 pypa/gh-action-pypi-publish@0ab0b79, though. So everything's good!
-- @webknjaz💰
🪞 Full Diff: pypa/gh-action-pypi-publish@v1.10.0...v1.10.1
🧔♂️ Release Manager: @webknjaz 🇺🇦
🙏 Special Thanks to @hugovk💰 for promptly validating the bug fix, mere minutes after I pushed it — I even haven't finished writing this text by then!
v1.10.0Compare Source
🔏 Anything fancy, eh?
This time, @woodruffw💰 implemented support for PEP 740 attestations functionality in #236 and #245. This is a big deal, as it is a huge step forward to replacing what the deprecated GPG signatures used to provide in a more meaningful way.
🙏 And please, thank William for working on this amazing improvement for the ecosystem! The overall effort is tracked @&#https://github.com/pypi/warehouse/issues/15871/15871, by the way.
🪞 Full Diff: pypa/gh-action-pypi-publish@v1.9.0...v1.10.0
🧔♂️ Release Manager: @webknjaz 🇺🇦
v1.9.0Compare Source
💅 Cosmetic Output Improvements
twine uploadcommand via #231🛠️ Internal Dependencies
cryptography == 42.0.7id == 1.4.0idna == 3.7via #228requests == 2.32.0via #240Twine == 5.1.0⚙️ Secret Stuff
In #241, @br3ndonland💰 added a Docker label linking the container image to this repository for GHCR to display it nicely. This is preparatory work for a big performance-focused refactoring he's working on in #230.
💪 New Contributors
🪞 Full Diff: pypa/gh-action-pypi-publish@v1.8.14...v1.9.0
🧔♂️ Release Manager: @webknjaz 🇺🇦
🙏 Special Thanks to @pradyunsg💰 for promptly unblocking this release to Marketplace as GitHub started asking for yet another developer agreement signature from the organization admins.
v1.8.14Compare Source
🛠️ Internal Dependencies
Nothing changed feature-wise. The only notable update is that the underlying container runtime now uses Python 3.12 and pip has been updated to v24.0 there.
This is should go unnoticed in terms of behavior. It's just a bit of maintenance burden to be done occasionally by @webknjaz💰.
Enjoy!
🪞 Full Diff: pypa/gh-action-pypi-publish@v1.8.13...v1.8.14
🧔♂️ Release Manager: @webknjaz 🇺🇦
v1.8.13Compare Source
🐛 What's Fixed
This action is now able to consume and publish distribution packages with
Metadata-Version: 2.3embedded.🛠️ Internal Dependencies
@SigureMo💰 sent us a bump of
pkginfoversion to version 1.10.0 in #219. It's a transitive dependency for us and is not an API-level change but upgrading it has a side effect of letting Twine recognize distribution packages declaringMetadata-Version: 2.3. In particular, it is known to affect distributions built withMaturin >= 1.5.0.Following that, @webknjaz💰 upgraded other transitive and direct dependency pins, including, among others, the following notable bumps:
cryptography == 42.0.5id == 1.3.0readme-renderer == 43.0Twine == 5.0.0💪 New Contributors
@SigureMo made their first contribution in https://github.com/pypa/gh-action-pypi-publish/pull/219
🪞 Full Diff: pypa/gh-action-pypi-publish@v1.8.12...v1.8.13
🧔♂️ Release Manager: @webknjaz 🇺🇦
v1.8.12Compare Source
💅 Cosmetic Output Improvements
@woodruffw💰 replaced the notice annotations with simplified debug messages related to authentication methanism selection via #196. The also improved the error clarity during OIDC exchange on PRs from forks via #203.
📝 What's Documented
@virtuald💰 updated the docs and pointer messages were updated to mention that reusable workflows aren't supported right now in #186 and @xuanzhi33💰 later corrected the markdown syntax there via #216.
🛠️ Internal Dependencies
⚙️ Secret Stuff
@woodruffw proactively updated the OIDC minting API endpoint used during the exchange via #206. Nothing you should be too concerned about, promise!
💪 New Contributors
🪞 Full Diff: pypa/gh-action-pypi-publish@v1.8.11...v1.8.12
🧔♂️ Release Manager: @webknjaz 🇺🇦
v1.8.11Compare Source
💅 Cosmetic output improvements
@woodruffw added a nudge suggesting the users storing passwords in a GitHub Actions repository secrets to switch to using secretless publishing in https://github.com/pypa/gh-action-pypi-publish/pull/190. This also reminds people that PyPI will start mandating two-factor authentication to perform uploads in 2024.
📝 What's Documented
@di linked the configuration docs for Trusted Publishing in README via https://github.com/pypa/gh-action-pypi-publish/pull/179.
🛠️ Internal dependencies
💪 New Contributors
🪞 Full Diff: pypa/gh-action-pypi-publish@v1.8.10...v1.8.11
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.