pypa/gh-action-pypi-publish (pypa/gh-action-pypi-publish)
### [`v1.10.3`](https://redirect.github.com/pypa/gh-action-pypi-publish/releases/tag/v1.10.3)
[Compare Source](https://redirect.github.com/pypa/gh-action-pypi-publish/compare/v1.10.2...v1.10.3)
#### π Cosmetic Output Improvements
In [#270](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/270), [@facutuesca](https://redirect.github.com/facutuesca)[π°](https://redirect.github.com/sponsors/facutuesca) made a follow-up to their previous PR [#250](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/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](https://redirect.github.com/mosfet80)[π°](https://redirect.github.com/sponsors/mosfet80) updated a few internal linter versions in [#266](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/266), [#267](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/267), and [#271](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/271), no user impact. This is usually automated otherwise.
#### πͺ New Contributors
- [@mosfet80](https://redirect.github.com/mosfet80) made their first contribution in [https://github.com/pypa/gh-action-pypi-publish/pull/266](https://redirect.github.com/pypa/gh-action-pypi-publish/pull/266)
**πͺ Full Diff**: https://github.com/pypa/gh-action-pypi-publish/compare/v1.10.2...v1.10.3
**π§ββοΈ Release Manager:** [@webknjaz πΊπ¦](https://redirect.github.com/sponsors/webknjaz)
### [`v1.10.2`](https://redirect.github.com/pypa/gh-action-pypi-publish/releases/tag/v1.10.2)
[Compare Source](https://redirect.github.com/pypa/gh-action-pypi-publish/compare/v1.10.1...v1.10.2)
#### π Cosmetic Output Improvements
In [#250](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/250) and [#258](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/258), [@facutuesca](https://redirect.github.com/facutuesca)[π°](https://redirect.github.com/sponsors/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](https://redirect.github.com/woodruffw)[π°](https://redirect.github.com/sponsors/woodruffw) bumped `pypi-attestations` to v0.0.12 in [#262](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/262), ~hopefully fixing [#263](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/263). π€~ Nah.. that wasn't it.
> \[!TIP]
> Please keep in mind that reusable workflows are not yet supported, even though they sometimes work, mostly by accident.
#### πͺ New Contributors
[@facutuesca](https://redirect.github.com/facutuesca) made their first contribution in [https://github.com/pypa/gh-action-pypi-publish/pull/258](https://redirect.github.com/pypa/gh-action-pypi-publish/pull/258)
**πͺ Full Diff**: https://github.com/pypa/gh-action-pypi-publish/compare/v1.10.1...v1.10.2
**π§ββοΈ Release Manager:** [@webknjaz πΊπ¦](https://redirect.github.com/sponsors/webknjaz)
**π Special Thanks** to [@henryiii](https://redirect.github.com/henryiii)[π°](https://redirect.github.com/sponsors/henryiii) for promptly pointing up possible fixes for [#263](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/263).
### [`v1.10.1`](https://redirect.github.com/pypa/gh-action-pypi-publish/releases/tag/v1.10.1)
[Compare Source](https://redirect.github.com/pypa/gh-action-pypi-publish/compare/v1.10.0...v1.10.1)
#### ππ 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 https://github.com/pypa/gh-action-pypi-publish/commit/0ab0b79, though. So everything's good!
\-- [@webknjaz](https://redirect.github.com/webknjaz)[π°](https://redirect.github.com/sponsors/webknjaz)
> \[!IMPORTANT]
> β¨ Despite this minor hiccup, we invite you to still opt into trying this feature out early. [It can be enabled](https://redirect.github.com/marketplace/actions/pypi-publish#generating-and-uploading-attestations) like this:
>
> ```yml
> with:
> attestations: true
> ```
>
> Leave feedback in [the v1.10.0 release discussion](https://redirect.github.com/pypa/gh-action-pypi-publish/discussions/255) or [the PR](https://redirect.github.com/pypa/gh-action-pypi-publish/pull/236).
**πͺ Full Diff**: https://github.com/pypa/gh-action-pypi-publish/compare/v1.10.0...v1.10.1
**π§ββοΈ Release Manager:** [@webknjaz πΊπ¦](https://redirect.github.com/sponsors/webknjaz)
**π Special Thanks** to [@hugovk](https://redirect.github.com/hugovk)[π°](https://redirect.github.com/sponsors/hugovk) for [promptly validating the bug fix](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/256#issuecomment-2325925847), mere minutes after I pushed it β I even haven't finished writing this text by then!
### [`v1.10.0`](https://redirect.github.com/pypa/gh-action-pypi-publish/releases/tag/v1.10.0)
[Compare Source](https://redirect.github.com/pypa/gh-action-pypi-publish/compare/v1.9.0...v1.10.0)
#### π Anything fancy, eh?
This time, [@woodruffw](https://redirect.github.com/woodruffw)[π°](https://redirect.github.com/sponsors/woodruffw) implemented support for [PEP 740] attestations functionality in [#236](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/236) and [#245](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/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](https://redirect.github.com/marketplace/actions/pypi-publish#generating-and-uploading-attestations) as follows:
>
> ```yml
> with:
> attestations: true
> ```
>
> Leave any feedback on this in [this release discussion](https://redirect.github.com/pypa/gh-action-pypi-publish/discussions/255) or [the PR](https://redirect.github.com/pypa/gh-action-pypi-publish/pull/236).
π 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](https://redirect.github.com/pypi/warehouse/issues/15871)/15871, by the way.
**πͺ Full Diff**: https://github.com/pypa/gh-action-pypi-publish/compare/v1.9.0...v1.10.0
**π§ββοΈ Release Manager:** [@webknjaz πΊπ¦](https://redirect.github.com/sponsors/webknjaz)
[PEP 740]: https://peps.python.org/pep-0740/
### [`v1.9.0`](https://redirect.github.com/pypa/gh-action-pypi-publish/releases/tag/v1.9.0)
[Compare Source](https://redirect.github.com/pypa/gh-action-pypi-publish/compare/v1.8.14...v1.9.0)
#### π Cosmetic Output Improvements
- [@woodruffw](https://redirect.github.com/woodruffw)[π°](https://redirect.github.com/sponsors/woodruffw) updated the tense on password nudge in [#234](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/234)
- [@shenxianpeng](https://redirect.github.com/shenxianpeng)[π°](https://redirect.github.com/sponsors/shenxianpeng) helped us disable the progress bar that was being produced by the `twine upload` command via [#231](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/231)
- [@woodruffw](https://redirect.github.com/woodruffw)[π°](https://redirect.github.com/sponsors/woodruffw) also linked the PyPI status dashboard in the trusted publishing error message via [https://github.com/pypa/gh-action-pypi-publish/pull/243](https://redirect.github.com/pypa/gh-action-pypi-publish/pull/243)
#### π οΈ Internal Dependencies
- pre-commit linters got auto-updated @ [#225](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/225)
- some notable dependency bumps include
- `cryptography == 42.0.7`
- `id == 1.4.0`
- `idna == 3.7` via [#228](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/228)
- `requests == 2.32.0` via [#240](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/240)
- `Twine == 5.1.0`
#### βοΈ Secret Stuff
In [#241](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/241), [@br3ndonland](https://redirect.github.com/br3ndonland)[π°](https://redirect.github.com/sponsors/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](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/230).
#### πͺ New Contributors
- [@shenxianpeng](https://redirect.github.com/shenxianpeng) made their first contribution in [https://github.com/pypa/gh-action-pypi-publish/pull/231](https://redirect.github.com/pypa/gh-action-pypi-publish/pull/231)
- [@br3ndonland](https://redirect.github.com/br3ndonland) made their first contribution in [https://github.com/pypa/gh-action-pypi-publish/pull/241](https://redirect.github.com/pypa/gh-action-pypi-publish/pull/241)
**πͺ Full Diff**: https://github.com/pypa/gh-action-pypi-publish/compare/v1.8.14...v1.9.0
**π§ββοΈ Release Manager:** [@webknjaz πΊπ¦](https://redirect.github.com/sponsors/webknjaz)
**π Special Thanks** to [@pradyunsg](https://redirect.github.com/pradyunsg)[π°](https://redirect.github.com/sponsors/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`](https://redirect.github.com/pypa/gh-action-pypi-publish/releases/tag/v1.8.14)
[Compare Source](https://redirect.github.com/pypa/gh-action-pypi-publish/compare/v1.8.13...v1.8.14)
#### π οΈ 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](https://redirect.github.com/webknjaz)[π°](https://redirect.github.com/sponsors/webknjaz).
*Enjoy!*
**πͺ Full Diff**: https://github.com/pypa/gh-action-pypi-publish/compare/v1.8.13...v1.8.14
**π§ββοΈ Release Manager:** [@webknjaz πΊπ¦](https://redirect.github.com/sponsors/webknjaz)
### [`v1.8.13`](https://redirect.github.com/pypa/gh-action-pypi-publish/releases/tag/v1.8.13)
[Compare Source](https://redirect.github.com/pypa/gh-action-pypi-publish/compare/v1.8.12...v1.8.13)
#### π What's Fixed
This action is now able to consume and publish distribution packages with `Metadata-Version: 2.3` embedded.
#### π οΈ Internal Dependencies
[@SigureMo](https://redirect.github.com/SigureMo)[π°](https://redirect.github.com/sponsors/SigureMo) sent us a bump of `pkginfo` version to version 1.10.0 in [#219](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/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`](https://packaging.python.org/en/latest/specifications/core-metadata/). In particular, it is known to affect distributions built with `Maturin >= 1.5.0`.
Following that, [@webknjaz](https://redirect.github.com/webknjaz)[π°](https://redirect.github.com/sponsors/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](https://redirect.github.com/SigureMo) made their first contribution in [https://github.com/pypa/gh-action-pypi-publish/pull/219](https://redirect.github.com/pypa/gh-action-pypi-publish/pull/219)
**πͺ Full Diff**: https://github.com/pypa/gh-action-pypi-publish/compare/v1.8.12...v1.8.13
**π§ββοΈ Release Manager:** [@webknjaz πΊπ¦](https://redirect.github.com/sponsors/webknjaz)
### [`v1.8.12`](https://redirect.github.com/pypa/gh-action-pypi-publish/releases/tag/v1.8.12)
[Compare Source](https://redirect.github.com/pypa/gh-action-pypi-publish/compare/v1.8.11...v1.8.12)
#### π Cosmetic Output Improvements
[@woodruffw](https://redirect.github.com/woodruffw)[π°](https://redirect.github.com/sponsors/woodruffw) replaced the notice annotations with simplified debug messages related to authentication methanism selection via [#196](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/196). The also improved the error clarity during OIDC exchange on PRs from forks via [#203](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/203).
#### π What's Documented
[@virtuald](https://redirect.github.com/virtuald)[π°](https://redirect.github.com/sponsors/virtuald) updated the docs and pointer messages were updated to mention that reusable workflows aren't supported right now in [#186](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/186) and [@xuanzhi33](https://redirect.github.com/xuanzhi33)[π°](https://redirect.github.com/sponsors/xuanzhi33) later corrected the markdown syntax there via [#216](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/216).
#### π οΈ Internal Dependencies
- pre-commit linters got autoupdated @ [#204](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/204)
- Cryptography was bumped from 41.0.6 to 42.0.4 @ [#210](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/210), [#213](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/213) and [#214](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/214)
#### βοΈ Secret Stuff
[@woodruffw](https://redirect.github.com/woodruffw) proactively updated the OIDC minting API endpoint used during the exchange via [#206](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/206). Nothing you should be too concerned about, promise!
#### πͺ New Contributors
- [@virtuald](https://redirect.github.com/virtuald) made their first contribution in [https://github.com/pypa/gh-action-pypi-publish/pull/186](https://redirect.github.com/pypa/gh-action-pypi-publish/pull/186)
- [@xuanzhi33](https://redirect.github.com/xuanzhi33) made their first contribution in [https://github.com/pypa/gh-action-pypi-publish/pull/216](https://redirect.github.com/pypa/gh-action-pypi-publish/pull/216)
**πͺ Full Diff**: https://github.com/pypa/gh-action-pypi-publish/compare/v1.8.11...v1.8.12
**:man_beard: Release Manager:** [@webknjaz πΊπ¦](https://redirect.github.com/sponsors/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.
[ ] If you want to rebase/retry this PR, check this box
This PR contains the following updates:
v1.8.11
->v1.10.3
Release Notes
pypa/gh-action-pypi-publish (pypa/gh-action-pypi-publish)
### [`v1.10.3`](https://redirect.github.com/pypa/gh-action-pypi-publish/releases/tag/v1.10.3) [Compare Source](https://redirect.github.com/pypa/gh-action-pypi-publish/compare/v1.10.2...v1.10.3) #### π Cosmetic Output Improvements In [#270](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/270), [@facutuesca](https://redirect.github.com/facutuesca)[π°](https://redirect.github.com/sponsors/facutuesca) made a follow-up to their previous PR [#250](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/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](https://redirect.github.com/mosfet80)[π°](https://redirect.github.com/sponsors/mosfet80) updated a few internal linter versions in [#266](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/266), [#267](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/267), and [#271](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/271), no user impact. This is usually automated otherwise. #### πͺ New Contributors - [@mosfet80](https://redirect.github.com/mosfet80) made their first contribution in [https://github.com/pypa/gh-action-pypi-publish/pull/266](https://redirect.github.com/pypa/gh-action-pypi-publish/pull/266) **πͺ Full Diff**: https://github.com/pypa/gh-action-pypi-publish/compare/v1.10.2...v1.10.3 **π§ββοΈ Release Manager:** [@webknjaz πΊπ¦](https://redirect.github.com/sponsors/webknjaz) ### [`v1.10.2`](https://redirect.github.com/pypa/gh-action-pypi-publish/releases/tag/v1.10.2) [Compare Source](https://redirect.github.com/pypa/gh-action-pypi-publish/compare/v1.10.1...v1.10.2) #### π Cosmetic Output Improvements In [#250](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/250) and [#258](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/258), [@facutuesca](https://redirect.github.com/facutuesca)[π°](https://redirect.github.com/sponsors/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](https://redirect.github.com/woodruffw)[π°](https://redirect.github.com/sponsors/woodruffw) bumped `pypi-attestations` to v0.0.12 in [#262](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/262), ~hopefully fixing [#263](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/263). π€~ Nah.. that wasn't it. > \[!TIP] > Please keep in mind that reusable workflows are not yet supported, even though they sometimes work, mostly by accident. #### πͺ New Contributors [@facutuesca](https://redirect.github.com/facutuesca) made their first contribution in [https://github.com/pypa/gh-action-pypi-publish/pull/258](https://redirect.github.com/pypa/gh-action-pypi-publish/pull/258) **πͺ Full Diff**: https://github.com/pypa/gh-action-pypi-publish/compare/v1.10.1...v1.10.2 **π§ββοΈ Release Manager:** [@webknjaz πΊπ¦](https://redirect.github.com/sponsors/webknjaz) **π Special Thanks** to [@henryiii](https://redirect.github.com/henryiii)[π°](https://redirect.github.com/sponsors/henryiii) for promptly pointing up possible fixes for [#263](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/263). ### [`v1.10.1`](https://redirect.github.com/pypa/gh-action-pypi-publish/releases/tag/v1.10.1) [Compare Source](https://redirect.github.com/pypa/gh-action-pypi-publish/compare/v1.10.0...v1.10.1) #### ππ 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 https://github.com/pypa/gh-action-pypi-publish/commit/0ab0b79, though. So everything's good! \-- [@webknjaz](https://redirect.github.com/webknjaz)[π°](https://redirect.github.com/sponsors/webknjaz) > \[!IMPORTANT] > β¨ Despite this minor hiccup, we invite you to still opt into trying this feature out early. [It can be enabled](https://redirect.github.com/marketplace/actions/pypi-publish#generating-and-uploading-attestations) like this: > > ```yml > with: > attestations: true > ``` > > Leave feedback in [the v1.10.0 release discussion](https://redirect.github.com/pypa/gh-action-pypi-publish/discussions/255) or [the PR](https://redirect.github.com/pypa/gh-action-pypi-publish/pull/236). **πͺ Full Diff**: https://github.com/pypa/gh-action-pypi-publish/compare/v1.10.0...v1.10.1 **π§ββοΈ Release Manager:** [@webknjaz πΊπ¦](https://redirect.github.com/sponsors/webknjaz) **π Special Thanks** to [@hugovk](https://redirect.github.com/hugovk)[π°](https://redirect.github.com/sponsors/hugovk) for [promptly validating the bug fix](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/256#issuecomment-2325925847), mere minutes after I pushed it β I even haven't finished writing this text by then! ### [`v1.10.0`](https://redirect.github.com/pypa/gh-action-pypi-publish/releases/tag/v1.10.0) [Compare Source](https://redirect.github.com/pypa/gh-action-pypi-publish/compare/v1.9.0...v1.10.0) #### π Anything fancy, eh? This time, [@woodruffw](https://redirect.github.com/woodruffw)[π°](https://redirect.github.com/sponsors/woodruffw) implemented support for [PEP 740] attestations functionality in [#236](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/236) and [#245](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/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](https://redirect.github.com/marketplace/actions/pypi-publish#generating-and-uploading-attestations) as follows: > > ```yml > with: > attestations: true > ``` > > Leave any feedback on this in [this release discussion](https://redirect.github.com/pypa/gh-action-pypi-publish/discussions/255) or [the PR](https://redirect.github.com/pypa/gh-action-pypi-publish/pull/236). π 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](https://redirect.github.com/pypi/warehouse/issues/15871)/15871, by the way. **πͺ Full Diff**: https://github.com/pypa/gh-action-pypi-publish/compare/v1.9.0...v1.10.0 **π§ββοΈ Release Manager:** [@webknjaz πΊπ¦](https://redirect.github.com/sponsors/webknjaz) [PEP 740]: https://peps.python.org/pep-0740/ ### [`v1.9.0`](https://redirect.github.com/pypa/gh-action-pypi-publish/releases/tag/v1.9.0) [Compare Source](https://redirect.github.com/pypa/gh-action-pypi-publish/compare/v1.8.14...v1.9.0) #### π Cosmetic Output Improvements - [@woodruffw](https://redirect.github.com/woodruffw)[π°](https://redirect.github.com/sponsors/woodruffw) updated the tense on password nudge in [#234](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/234) - [@shenxianpeng](https://redirect.github.com/shenxianpeng)[π°](https://redirect.github.com/sponsors/shenxianpeng) helped us disable the progress bar that was being produced by the `twine upload` command via [#231](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/231) - [@woodruffw](https://redirect.github.com/woodruffw)[π°](https://redirect.github.com/sponsors/woodruffw) also linked the PyPI status dashboard in the trusted publishing error message via [https://github.com/pypa/gh-action-pypi-publish/pull/243](https://redirect.github.com/pypa/gh-action-pypi-publish/pull/243) #### π οΈ Internal Dependencies - pre-commit linters got auto-updated @ [#225](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/225) - some notable dependency bumps include - `cryptography == 42.0.7` - `id == 1.4.0` - `idna == 3.7` via [#228](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/228) - `requests == 2.32.0` via [#240](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/240) - `Twine == 5.1.0` #### βοΈ Secret Stuff In [#241](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/241), [@br3ndonland](https://redirect.github.com/br3ndonland)[π°](https://redirect.github.com/sponsors/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](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/230). #### πͺ New Contributors - [@shenxianpeng](https://redirect.github.com/shenxianpeng) made their first contribution in [https://github.com/pypa/gh-action-pypi-publish/pull/231](https://redirect.github.com/pypa/gh-action-pypi-publish/pull/231) - [@br3ndonland](https://redirect.github.com/br3ndonland) made their first contribution in [https://github.com/pypa/gh-action-pypi-publish/pull/241](https://redirect.github.com/pypa/gh-action-pypi-publish/pull/241) **πͺ Full Diff**: https://github.com/pypa/gh-action-pypi-publish/compare/v1.8.14...v1.9.0 **π§ββοΈ Release Manager:** [@webknjaz πΊπ¦](https://redirect.github.com/sponsors/webknjaz) **π Special Thanks** to [@pradyunsg](https://redirect.github.com/pradyunsg)[π°](https://redirect.github.com/sponsors/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`](https://redirect.github.com/pypa/gh-action-pypi-publish/releases/tag/v1.8.14) [Compare Source](https://redirect.github.com/pypa/gh-action-pypi-publish/compare/v1.8.13...v1.8.14) #### π οΈ 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](https://redirect.github.com/webknjaz)[π°](https://redirect.github.com/sponsors/webknjaz). *Enjoy!* **πͺ Full Diff**: https://github.com/pypa/gh-action-pypi-publish/compare/v1.8.13...v1.8.14 **π§ββοΈ Release Manager:** [@webknjaz πΊπ¦](https://redirect.github.com/sponsors/webknjaz) ### [`v1.8.13`](https://redirect.github.com/pypa/gh-action-pypi-publish/releases/tag/v1.8.13) [Compare Source](https://redirect.github.com/pypa/gh-action-pypi-publish/compare/v1.8.12...v1.8.13) #### π What's Fixed This action is now able to consume and publish distribution packages with `Metadata-Version: 2.3` embedded. #### π οΈ Internal Dependencies [@SigureMo](https://redirect.github.com/SigureMo)[π°](https://redirect.github.com/sponsors/SigureMo) sent us a bump of `pkginfo` version to version 1.10.0 in [#219](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/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`](https://packaging.python.org/en/latest/specifications/core-metadata/). In particular, it is known to affect distributions built with `Maturin >= 1.5.0`. Following that, [@webknjaz](https://redirect.github.com/webknjaz)[π°](https://redirect.github.com/sponsors/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](https://redirect.github.com/SigureMo) made their first contribution in [https://github.com/pypa/gh-action-pypi-publish/pull/219](https://redirect.github.com/pypa/gh-action-pypi-publish/pull/219) **πͺ Full Diff**: https://github.com/pypa/gh-action-pypi-publish/compare/v1.8.12...v1.8.13 **π§ββοΈ Release Manager:** [@webknjaz πΊπ¦](https://redirect.github.com/sponsors/webknjaz) ### [`v1.8.12`](https://redirect.github.com/pypa/gh-action-pypi-publish/releases/tag/v1.8.12) [Compare Source](https://redirect.github.com/pypa/gh-action-pypi-publish/compare/v1.8.11...v1.8.12) #### π Cosmetic Output Improvements [@woodruffw](https://redirect.github.com/woodruffw)[π°](https://redirect.github.com/sponsors/woodruffw) replaced the notice annotations with simplified debug messages related to authentication methanism selection via [#196](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/196). The also improved the error clarity during OIDC exchange on PRs from forks via [#203](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/203). #### π What's Documented [@virtuald](https://redirect.github.com/virtuald)[π°](https://redirect.github.com/sponsors/virtuald) updated the docs and pointer messages were updated to mention that reusable workflows aren't supported right now in [#186](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/186) and [@xuanzhi33](https://redirect.github.com/xuanzhi33)[π°](https://redirect.github.com/sponsors/xuanzhi33) later corrected the markdown syntax there via [#216](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/216). #### π οΈ Internal Dependencies - pre-commit linters got autoupdated @ [#204](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/204) - Cryptography was bumped from 41.0.6 to 42.0.4 @ [#210](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/210), [#213](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/213) and [#214](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/214) #### βοΈ Secret Stuff [@woodruffw](https://redirect.github.com/woodruffw) proactively updated the OIDC minting API endpoint used during the exchange via [#206](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/206). Nothing you should be too concerned about, promise! #### πͺ New Contributors - [@virtuald](https://redirect.github.com/virtuald) made their first contribution in [https://github.com/pypa/gh-action-pypi-publish/pull/186](https://redirect.github.com/pypa/gh-action-pypi-publish/pull/186) - [@xuanzhi33](https://redirect.github.com/xuanzhi33) made their first contribution in [https://github.com/pypa/gh-action-pypi-publish/pull/216](https://redirect.github.com/pypa/gh-action-pypi-publish/pull/216) **πͺ Full Diff**: https://github.com/pypa/gh-action-pypi-publish/compare/v1.8.11...v1.8.12 **:man_beard: Release Manager:** [@webknjaz πΊπ¦](https://redirect.github.com/sponsors/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.