Releases: pypa/gh-action-pypi-publish
Release list
v1.8.9
💅 Cosmetic output improvements
- @woodruffw added debug output to the trusted publishing OIDC exchange on failures in #174
- @woodruffw implemented Markdown semantic callouts in README via #175
🛠️ Internal dependencies
- Certifi was bumped from 2023.5.7 to 2023.7.22 @ #171
- Cryptography was bumped from 41.0.2 to 41.0.3 @ #172
Full Diff: v1.8.8...v1.8.9
Contributors
Assets 2
v1.8.8
💅 Cosmetic output improvements
-
In #167, @woodruffw introduced a nudge-warning encouraging people to start using secretless publishing to PyPI, as suggested by @sethmlarson in #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
💪 New Contributors
🪞 Full Diff: v1.8.7...v1.8.8
Contributors
Assets 2
v1.8.7
💅 Cosmetic output impovements
- @woodruffw fixed OIDC the multiline annotations by escaping LF through urlencoding it in #156.
- @jaap3 noticed and promptly removed extraneous
}from a non-OIDC log annotation in #161. - @hugovk made pip ignore that it runs under the root user and suppress its warning output in #159.
🛠️ Internal dependencies
- Cryptography was bumped from 39.0.1 to 41.0.0 @ #160
- Requests was bumped from 2.28.1 to 2.31.0 @ #157
💪 New Contributors
🪞 Full Diff: v1.8.6...v1.8.7
Contributors
Assets 2
v1.8.6
What's Updated
- @woodruffw dropped the references to a “private beta” from the project docs and runtime in #147. He also clarified that the API tokens are still more secure than passwords in #150.
- @asherf noticed that the action metadata incorrectly marked the
passwordfield as required and contributed a correction in #151 - @webknjaz moved the Trusted Publishing example to the top of the README in hopes that new users would default to using it via f47b347
New Contributors
Full Diff: v1.8.5...v1.8.6
v1.8.5
What's Improved
@woodruffw improved the user-facing documentation and logging to make use of the Trusted Publishing flow terminology cohesive with PyPI in #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 #142.
Full Diff: v1.8.4...v1.8.5
Contributors
Assets 2
v1.8.4
What's Improved
- @hugovk cleaned up the double whitespaces in the OIDC flow logging in #140
- @woodruffw added a title and a docs link to the OIDC error output in #139
Full Diff: v1.8.3...v1.8.4
Contributors
Assets 2
v1.8.3
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 #136.
Full Diff: v1.8.2...v1.8.3
Contributors
Assets 2
v1.8.2
What's Changed
This release started printing out full OIDC error messages to console, instead of just one line -- by @woodruffw in #134.
Full Diff: v1.8.1...v1.8.2
Contributors
Assets 2
v1.8.1
🐛 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 #131
Full Diff: v1.8.0...v1.8.1
Contributors
Assets 2
v1.8.0
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: pypi/warehouse#12965
New Contributors
- @woodruffw made their first contribution in #123
Full Diff: v1.7.1...v1.8.0