Bump pypa/gh-action-pypi-publish from 1.8.3 to 1.8.5

[dependabot[bot]]

Bumps pypa/gh-action-pypi-publish from 1.8.3 to 1.8.5.

Release notes

Sourced from pypa/gh-action-pypi-publish's releases.

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 pypa/gh-action-pypi-publish#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 pypa/gh-action-pypi-publish#142.

Full Diff: https://github.com/pypa/gh-action-pypi-publish/compare/v1.8.4...v1.8.5

v1.8.4

What's Improved

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

Full Diff: https://github.com/pypa/gh-action-pypi-publish/compare/v1.8.3...v1.8.4

Commits

• 0bf742b Merge pull request #143 from trail-of-forks/tob-rewrite-oidc-refs
• 30c3822 oidc-exchange: another link
• 89ddbea README: retitle, add note
• a0f29a5 Apply suggestions from code review
• 0b567d5 oidc-exchange, twine-upload: remove more OIDC refs
• 4372cb5 README: replace OIDC with "trusted publishing"
• 69efb8c Merge pull request #142 from trail-of-forks/tob-indicate-oidc
• dfde872 Apply suggestions from code review
• 3d567f4 twine-upload: expound
• 67b747a oidc-exchange: more explanation
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions[bot]]

:point_left: Launch a binder notebook on branch _s-weigand/flake8-nb/dependabot/githubactions/pypa/gh-action-pypi-publish-1.8.5

[codecov[bot]]

Codecov Report

Patch and project coverage have no change.

Comparison is base (c56ce8d) 100.00% compared to head (e0f89fe) 100.00%.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #301 +/- ## ========================================= Coverage 100.00% 100.00% ========================================= Files 5 5 Lines 431 431 Branches 72 72 ========================================= Hits 431 431 ``` Help us with your feedback. Take ten seconds to tell us [how you rate us](https://about.codecov.io/nps?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=Sebastian+Weigand). Have a feature suggestion? [Share it here.](https://app.codecov.io/gh/feedback/?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=Sebastian+Weigand)

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.