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

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
pypa/gh-action-pypi-publish	action	minor	v1.6.4 -> v1.8.5

---

Release Notes

pypa/gh-action-pypi-publish

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.

Setup prerequisites: https://github.com/marketplace/actions/pypi-publish#publishing-with-openid-connect
PyPI's documentation: https://pypi.org/help/#openid-connect
Beta test enrollment: https://github.com/pypi/warehouse/issues/12965

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

---

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 has been generated by Mend Renovate. View repository job log here.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.