chore(deps): update pypa/gh-action-pypi-publish action to v1.12.4

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
pypa/gh-action-pypi-publish	action	minor	v1.4.2 -> v1.12.4

---

Release Notes

pypa/gh-action-pypi-publish (pypa/gh-action-pypi-publish)

v1.12.4

Compare Source

Be nice to FOSS maintainers.

✨ What's Changed

The main theme of this patch release that the support for uploading PEP 639 licensing metadata to PyPI has been fixed in #​327.

🛠️ Internal Updates

A few smaller updates include the attestation existence being checked earlier in the process now, listing all the violating files together, not just one (PR #​315).
And the lock file with the software available in runtime has been re-pinned in #​329.
Additionally, the CI now runs the smoke-tests against both Ubuntu 22.04 and 24.04 explicitly via da900af.

🪞 Full Diff: pypa/gh-action-pypi-publish@v1.12.3...v1.12.4

🧔‍♂️ Release Manager: @​webknjaz 🇺🇦

🙏 Special Thanks to @​dnicolodi💰 and @​woodruffw💰 for releasing the license metadata support fix in Twine!

💬 Discuss on Bluesky 🦋, on Mastodon 🐘 and on GitHub.

v1.12.3

Compare Source

✨ What's Improved

With the updates by @​woodruffw💰 and @​webknjaz💰 via #​309 and #​313, it is now possible to publish distribution packages that include core metadata v2.4, like those built using maturin. This is done by bumping Twine to v6.0.1 and pkginfo to v1.12.0.

📝 Docs

We've made an attempt to clarify the runtime and workflow shape that are expected to be supported for calling this action in: https://github.com/marketplace/actions/pypi-publish#Non-goals.

[!TIP]
Please, let us know in the release discussion if anything still remains unclear.
TL;DR always call [pypi-publish][pypi-publish] once per job; don't invoke it in reusable workflows; physically move building the dists into separate jobs having restricted permissions and storing the dists as GitHub Actions artifacts; when using self-hosted runners, make sure to still use [pypi-publish][pypi-publish] on a GitHub-provided infra with runs-on: ubuntu-latest, while building and testing may remain self-hosted; don't perform any other actions in the publishing job; don't call [pypi-publish][pypi-publish] from composite actions.

🛠️ Internal Updates

@​br3ndonland💰 improved the container image generation automation to include Git SHA in #​301. And @​woodruffw💰 added the workflow_ref context to Trusted Publishing debug logging in #​305, helping us diagnose misconfigurations faster. #​313 also extends the smoke test in the CI to check against the maturin-made dists. Additionally, jeepney and secretstorage transitive deps have been added to the pip constraint-based lock file, as Dependabot seems to have missed those earlier.

🪞 Full Diff: pypa/gh-action-pypi-publish@v1.12.2...v1.12.3

🧔‍♂️ Release Manager: @​webknjaz 🇺🇦

🙏 Special Thanks to @​samuelcolvin💰 for nudging me to cut this release sooner and for sponsoring me via @​pydantic💰!

🔌 Shameless Plug: The other day I've made this 🦋 Bluesky 🇺🇦 FOSS Maintainers Starter Pack subscribe to read news from people like me :)

💬 Discuss on Bluesky 🦋, on Mastodon 🐘 and on GitHub.

v1.12.2

Compare 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-attestations from 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.1

Compare 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 .zip sdists 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.0

Compare 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.

[!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: pypa/gh-action-pypi-publish@v1.11.0...v1.12.0

🧔‍♂️ Release Manager: @​webknjaz 🇺🇦

v1.11.0

Compare 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 sigstore to v3.5.1 and pypi-attestations to 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.3

Compare 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

• @​mosfet80 made their first contribution in https://github.com/pypa/gh-action-pypi-publish/pull/266

🪞 Full Diff: pypa/gh-action-pypi-publish@v1.10.2...v1.10.3

🧔‍♂️ Release Manager: @​webknjaz 🇺🇦

v1.10.2

Compare 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-attestations to v0.0.12 in #​262, fixing #​263.

[!TIP]
Please keep in mind that reusable workflows are not yet supported, even though they sometimes work, mostly by accident.

💪 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.1

Compare 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💰

[!IMPORTANT]
✨ Despite this minor hiccup, we invite you to still opt into trying this feature out early. It can be enabled like this:

  with:
    attestations: true

Leave feedback in the v1.10.0 release discussion or the PR.

🪞 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.0

Compare 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.

[!IMPORTANT]
✨ Please, do opt into trying this feature out early. It can be enabled as follows:

  with:
    attestations: true

Leave any feedback on this in this release discussion or the PR.

🙏 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.0

Compare Source

💅 Cosmetic Output Improvements

• @​woodruffw💰 updated the tense on password nudge in #​234
• @​shenxianpeng💰 helped us disable the progress bar that was being produced by the twine upload command via #​231
• @​woodruffw💰 also linked the PyPI status dashboard in the trusted publishing error message via https://github.com/pypa/gh-action-pypi-publish/pull/243

🛠️ Internal Dependencies

• pre-commit linters got auto-updated @​ #​225
• some notable dependency bumps include
  • cryptography == 42.0.7
  • id == 1.4.0
  • idna == 3.7 via #​228
  • requests == 2.32.0 via #​240
  • Twine == 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

• @​shenxianpeng made their first contribution in https://github.com/pypa/gh-action-pypi-publish/pull/231
• @​br3ndonland made their first contribution in https://github.com/pypa/gh-action-pypi-publish/pull/241

🪞 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.14

Compare 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.13

Compare Source

🐛 What's Fixed

This action is now able to consume and publish distribution packages with Metadata-Version: 2.3 embedded.

🛠️ Internal Dependencies

@​SigureMo💰 sent us a bump of pkginfo version 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 declaring Metadata-Version: 2.3. In particular, it is known to affect distributions built with Maturin >= 1.5.0.

Following that, @​webknjaz💰 upgraded other transitive and direct dependency pins, including, among others, the following notable bumps:

• cryptography == 42.0.5
• id == 1.3.0
• readme-renderer == 43.0
• Twine == 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.12

Compare 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

• pre-commit linters got autoupdated @​ #​204
• Cryptography was bumped from 41.0.6 to 42.0.4 @​ #​210, #​213 and #​214

⚙️ 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

• @​virtuald made their first contribution in https://github.com/pypa/gh-action-pypi-publish/pull/186
• @​xuanzhi33 made their first contribution in https://github.com/pypa/gh-action-pypi-publish/pull/216

🪞 Full Diff: pypa/gh-action-pypi-publish@v1.8.11...v1.8.12

🧔‍♂️ Release Manager: @​webknjaz 🇺🇦

v1.8.11

Compare 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

• Cryptography was bumped from 41.0.3 to 41.0.6 @&#https://github.com/pypa/gh-action-pypi-publish/pull/194ll/194
• Pip was bumped from 22.3.1 to 23.3 @&#https://github.com/pypa/gh-action-pypi-publish/pull/189ll/189
• pre-commit linters got autoupdated @&#https://github.com/pypa/gh-action-pypi-publish/pull/184ll/184
• Urllib3 was bumped from 2.0.3 to 2.0.7 @&#https://github.com/pypa/gh-action-pypi-publish/pull/183ll/18https://github.com/pypa/gh-action-pypi-publish/pull/185ll/185

💪 New Contributors

• @​di made their first contribution in https://github.com/pypa/gh-action-pypi-publish/pull/179

🪞 Full Diff: pypa/gh-action-pypi-publish@v1.8.10...v1.8.11

v1.8.10

Compare Source

🐛 What's Fixed

@​woodruffw fixed decoding OIDC claims in debug output on failure by applying correct padding to the encoded payload via https://github.com/pypa/gh-action-pypi-publish/pull/177.

Full Diff: pypa/gh-action-pypi-publish@v1.8.9...v1.8.10

v1.8.9

Compare Source

💅 Cosmetic output improvements

• @​woodruffw added debug output to the trusted publishing OIDC exchange on failures in https://github.com/pypa/gh-action-pypi-publish/pull/174
• @​woodruffw implemented Markdown semantic callouts in README via https://github.com/pypa/gh-action-pypi-publish/pull/175

🛠️ Internal dependencies

• Certifi was bumped from 2023.5.7 to 2023.7.22 @&#https://github.com/pypa/gh-action-pypi-publish/pull/171ll/171
• Cryptography was bumped from 41.0.2 to 41.0.3 @&#https://github.com/pypa/gh-action-pypi-publish/pull/172ll/172

Full Diff: pypa/gh-action-pypi-publish@v1.8.8...v1.8.9

v1.8.8

Compare Source

💅 Cosmetic output improvements

• In https://github.com/pypa/gh-action-pypi-publish/pull/167, @​woodruffw introduced a nudge-warning encouraging people to start using secretless publishing to PyPI, as suggested by @​sethmlarson in https://github.com/pypa/gh-action-pypi-publish/issues/164, collaborating with @​di.

  💡 Tip: The OIDC-based trusted publishing integration details can be found in the action README at https://github.com/marketplace/actions/pypi-publish#trusted-publishing and on the PyPI docs page at https://docs.pypi.org/trusted-publishers/. It's gone GA on April 20, 2023, during PyCon: https://blog.pypi.org/posts/2023-04-20-introducing-trusted-publishers/. And the Trail Of Bits blog post has some deeper explanation here: https://blog.trailofbits.com/2023/05/23/trusted-publishing-a-new-benchmark-for-packaging-security/.

🛠️ Internal dependencies

• @​pquentin bumped the runtime dependency pins to the recent versions @&#https://github.com/pypa/gh-action-pypi-publish/pull/168ll/168.

💪 New Contributors

• @​pquentin made their first contribution in https://github.com/pypa/gh-action-pypi-publish/pull/168

🪞 Full Diff: pypa/gh-action-pypi-publish@v1.8.7...v1.8.8

v1.8.7

Compare Source

💅 Cosmetic output impovements

• @​woodruffw fixed OIDC the multiline annotations by escaping LF through urlencoding it in https://github.com/pypa/gh-action-pypi-publish/pull/156.
• @​jaap3 noticed and promptly removed extraneous } from a non-OIDC log annotation in https://github.com/pypa/gh-action-pypi-publish/pull/161.
• @​hugovk made pip ignore that it runs under the root user and suppress its warning output in https://github.com/pypa/gh-action-pypi-publish/pull/159.

🛠️ Internal dependencies

• Cryptography was bumped from 39.0.1 to 41.0.0 @&#https://github.com/pypa/gh-action-pypi-publish/pull/160ll/160
• Requests was bumped from 2.28.1 to 2.31.0 @&#https://github.com/pypa/gh-action-pypi-publish/pull/157ll/157

💪 New Contributors

• @​jaap3 made their first contribution in https://github.com/pypa/gh-action-pypi-publish/pull/161

🪞 Full Diff: pypa/gh-action-pypi-publish@v1.8.6...v1.8.7

v1.8.6

Compare Source

What's Updated

• @​woodruffw dropped the references to a “private beta” from the project docs and runtime in https://github.com/pypa/gh-action-pypi-publish/pull/147. He also clarified that the API tokens are still more secure than passwords in https://github.com/pypa/gh-action-pypi-publish/pull/150.
• @​asherf noticed that the action metadata incorrectly marked the password field as required and contributed a correction in https://github.com/pypa/gh-action-pypi-publish/pull/151
• @​webknjaz moved the Trusted Publishing example to the top of the README in hopes that new users would default to using it via pypa/gh-action-pypi-publish@f47b347

New Contributors

• @​asherf made their first contribution in https://github.com/pypa/gh-action-pypi-publish/pull/151

Full Diff: pypa/gh-action-pypi-publish@v1.8.5...v1.8.6

v1.8.5

Compare Source

What's Improved

@​woodruffw improved the user-facing documentation and logging to make use of the Trusted Publishing flow terminology cohesive with PyPI in https://github.com/pypa/gh-action-pypi-publish/pull/143. Trusted Publishing used to be referred to as OpenID Connect (OIDC) — the underlying technology that is being used to make it work. He also made the action display the cause of the Trusted Publishing flow being selected by the action via https://github.com/pypa/gh-action-pypi-publish/pull/142.

Full Diff: pypa/gh-action-pypi-publish@v1.8.4...v1.8.5

v1.8.4

Compare Source

What's Improved

• @​hugovk cleaned up the double whitespaces in the OIDC flow logging in https://github.com/pypa/gh-action-pypi-publish/pull/140
• @​woodruffw added a title and a docs link to the OIDC error output in https://github.com/pypa/gh-action-pypi-publish/pull/139

Full Diff: pypa/gh-action-pypi-publish@v1.8.3...v1.8.4

v1.8.3

Compare Source

What's New

This release improves the logging detalization of which authentication mode is selected when the action runs. It surfaces this detail to the workflow run summary page as annotations. The change was contributed by @​woodruffw in https://github.com/pypa/gh-action-pypi-publish/pull/136.

Full Diff: pypa/gh-action-pypi-publish@v1.8.2...v1.8.3

v1.8.2

Compare Source

What's Changed

This release started printing out full OIDC error messages to console, instead of just one line -- by @​woodruffw in https://github.com/pypa/gh-action-pypi-publish/pull/134.

Full Diff: pypa/gh-action-pypi-publish@v1.8.1...v1.8.2

v1.8.1

Compare Source

🐛 What's Fixed

💔 Unfortunately, a tiny mistake in v1.8.0 caused a far-reaching regression for the most used code path.
❗ But don't worry, it's fixed now thanks to @​njzjz who promptly spotted it and @​zhongjiajie who sent a bugfix.

🙌 New Contributors

• @​zhongjiajie made their first contribution in https://github.com/pypa/gh-action-pypi-publish/pull/131

Full Diff: pypa/gh-action-pypi-publish@v1.8.0...v1.8.1

v1.8.0

Compare Source

The Coolest Release Ever!

In this release, @​woodruffw implemented support for secretless OIDC-based publishing to PyPI-like package indexes. The OIDC flow is activated when neither username nor password action inputs are set.

The OIDC “token exchange”, is an authentication technique that PyPI (and TestPyPI, and hopefully some future others) supports as an alternative to long-lived username/password combinations or long-lived API tokens.

~IMPORTANT: The PyPI-side configuration is only available to participants of the private beta test. Please, only try out the zero-config mode if you are a beta test participant having followed the PyPI configuration instructions.~
It's gone GA during Python 2023 and is available to everyone now.

Setup prerequisites: https://github.com/marketplace/actions/pypi-publish#trusted-publishing
PyPI's documentation: https://pypi.org/help/#trusted-publishers
~Beta test enrollment:https://github.com/pypi/warehouse/issues/129655~

New Contributors

• @​woodruffw made their first contribution in https://github.com/pypa/gh-action-pypi-publish/pull/123

Full Diff: pypa/gh-action-pypi-publish@v1.7.1...v1.8.0

v1.7.1

Compare Source

Regression?

There was a small setback with v1.7.0 — the snake_case fallbacks didn't work because the check for the kebab-case env vars with default values set was always truthy. This bugfix release promptly fixes that.

Full Diff: pypa/gh-action-pypi-publish@v1.7.0...v1.7.1

v1.7.0

Compare Source

What should I care about?

TL;DR The action input names have been converted to use kebab-case and marked deprecated. But the old names still work.

This is made to align the public API with the de-facto conventions in the ecosystem. We've used snake_case names, which the maintainer considers a historical mistake. New kebab-case inputs will make the end-users' workflows look more consistent and and visually distinguishable from other identifiers one may encounter in YAML.

There is no timeline for removing the old names, but it will happen in v3 or later versions of the action. If the maintainer doesn't forget to do this, that is.

The patch is here: https://github.com/pypa/gh-action-pypi-publish/pull/125.

Full Diff: pypa/gh-action-pypi-publish@v1.6.5...v1.7.0

v1.6.5

Compare Source

What's Changed

• Added an explicit warning when the password passed into the action is empty — thanks @​colindean

New Contributors

• @​colindean made their first contribution in https://github.com/pypa/gh-action-pypi-publish/pull/122

Full Diff: pypa/gh-action-pypi-publish@v1.6.4...v1.6.5

v1.6.4

Compare Source

oh, boi! again?

This is the last one tonight, promise! It fixes this embarrassing bug that was actually caught by the CI but got overlooked due to the lack of sleep.
TL;DR GH passed $HOME from the external env into the container and that tricked the Python's site module to think that the home directory is elsewhere, adding non-existent paths to the env vars. See #​115.

Full Diff: pypa/gh-action-pypi-publish@v1.6.3...v1.6.4

v1.6.3

Compare Source

Another Release!? Why?

In https://github.com/pypa/gh-action-pypi-publish/issues/112#issuecomment-1340133013, it was discovered that passing a $PATH variable even breaks the shebang. So this version adds more safeguards to make sure it keeps working with a fully broken $PATH.

Full Diff: pypa/gh-action-pypi-publish@v1.6.2...v1.6.3

v1.6.2

Compare Source

What's Fixed

• Made the $PATH and $PYTHONPATH environment variables resilient to broken values passed from the host runner environment, which previously allowed the users to accidentally break the container's internal runtime as reported in https://github.com/pypa/gh-action-pypi-publish/issues/112

Internal Maintenance Improvements

• Added a devpi-based smoke-test GitHub Actions CI/CD workflow by @​sesdaile-varmour in https://github.com/pypa/gh-action-pypi-publish/pull/111

New Contributors

• @​sesdaile-varmour made their first contribution in https://github.com/pypa/gh-action-pypi-publish/pull/111

Full Diff: pypa/gh-action-pypi-publish@v1.6.1...v1.6.2

v1.6.1

Compare Source

What's happened?!

There was a sneaky bug in v1.6.0 which caused Twine to be outside the import path in the Python runtime. It is fixed in v1.6.1 by updating $PYTHONPATH to point to a correct location of the user-global site-packages/ directory.

Full Diff: pypa/gh-action-pypi-publish@v1.6.0...v1.6.1

v1.6.0

Compare Source

Anything's changed?

The only update is that the Python runtime has been upgraded from 3.9 to 3.11. There are no functional changes in this release.

Full Changelog: pypa/gh-action-pypi-publish@v1.5.2...v1.6.0

v1.5.2

Compare Source

What's Improved

• Implemented the Twine transitive dependency tree pinning using pip-tools-generated constraint files. See https://github.com/pypa/gh-action-pypi-publish/issues/107 and https://github.com/pypa/gh-action-pypi-publish/issues/101 for details.

Full Diff: pypa/gh-action-pypi-publish@v1.5.1...v1.5.2

v1.5.1

Compare Source

What's Changed

• Fixed printing out the dist hashes when packages_dir is a wildcard value. — by @​dukecat0 in https://github.com/pypa/gh-action-pypi-publish/pull/91

Full Diff: pypa/gh-action-pypi-publish@v1.5.0...v1.5.1

v1.5.0

Compare Source

What's Changed

• Added an action input print_hash for showing the hash values of files to be uploaded — by @​meowmeowmeowcat in https://github.com/pypa/gh-action-pypi-publish/pull/87

New Contributors

• @​pllim made their first contribution in https://github.com/pypa/gh-action-pypi-publish/pull/55
• @​meowmeowmeowcat made their first contribution in https://github.com/pypa/gh-action-pypi-publish/pull/87

Full Diff: pypa/gh-action-pypi-publish@v1.4.2...v1.5.0

---

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 was generated by Mend Renovate. View the repository job log.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 82.75%. Comparing base (375b041) to head (e6cbe36).
Report is 5 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #52      +/-   ##
==========================================
- Coverage   82.95%   82.75%   -0.20%     
==========================================
  Files           2        2              
  Lines          88       87       -1     
==========================================
- Hits           73       72       -1     
  Misses         15       15              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.