Bump pypa/gh-action-pypi-publish from 1.2.2 to 1.13.0 in /.github/workflows

[dependabot]

Bumps pypa/gh-action-pypi-publish from 1.2.2 to 1.13.0.

Release notes

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

v1.13.0

[!important] 🚨 This release includes fixes for GHSA-vxmw-7h4f-hqxh discovered by @​woodruffw💰. We've also integrated Zizmor to catch similar issues in the future and you should too.

✨ New Stuff

@​woodruffw💰 updated the README to no longer mention the attestations feature being experimental in #347: it's been rather stable for a year already 🎉 He also added more diagnostic output which includes printing out the GitHub Environment claim via #371 and warning about the unsupported reusable workflows configurations #306, when using Trusted Publishing.

[!tip] The official support for reusable workflows is currently blocked on changes to PyPI. To get updates about progress on the action side, you may want to subscribe to #166. At PyCon US 2025 Sprints, @​facutuesca💰, @​miketheman💰, @​woodruffw💰 and I💰 spent several hours IRL brainstorming how to fix this and migrate projects that happen to rely on an obscure corner case with reusable workflows that temporarily allows them to function by accident. The result of that discussion is posted @ pypi/warehouse#11096. Note that this is a volunteer-led effort and there is no ETA. If you need this soon, make your employer sponsor the PSF and maybe they'll be able to hire somebody for this work on Warehouse.

In addition to that, @​konstin💰 sent #378 to pin actions/setup-python to a SHA hash. This makes pypi-publish compatible with new GitHub policies that allow organizations to mandate hash-pinning actions used in workflows.

🛠️ Internal Dependencies

@​webknjaz💰 made a bunch of updates to the action runtime which includes bumping it to Python 3.13 in #331 and updating the dependency tree across the board. pip-with-requires-python is no longer being installed (#332). Some related bumps were contributed by @​woodruffw💰 (#359) and @​kurtmckee💰 sent a contributor-facing PR, bumping the linting configuration via #335.

💪 New Contributors

• @​kurtmckee made their first contribution in #335
• @​konstin made their first contribution in #378

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

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

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

v1.12.4

... (truncated)

Commits

• ed0c539 📦📌 Bump the pinned dependency tree
• 77db1b7 Merge branch PR #306, GHSA-vxmw-7h4f-hqxh fix and PR #378 into unstable/v1
• 280b3a1 Alias typing as t in imports
• e380240 Use object in place of typing.Any in annotations
• e50bff6 Deduplicate claim ref lookup
• decbc9a Hint people to subscribe to #166 for notifications
• 8208ad3 Ask not to report bugs with reusable workflow
• ff0fef5 🧪 Scope WPS202 suppression to specific files
• 1293b8c Use yamllint disable line length lint
• ed01280 Linter (different rule)
• Additional commits viewable in compare view

You can trigger a rebase of this PR 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[claude]

Claude finished @dependabot[bot]'s task —— View job

---

PR Review Complete ✅

Review Summary

This Dependabot PR updates pypa/gh-action-pypi-publish from v1.2.2 to v1.13.0. Overall, this is a recommended security update that should be merged.

Security Assessment 🔒

HIGH PRIORITY: This update includes fixes for security advisory GHSA-vxmw-7h4f-hqxh. The release notes specifically mention:

• Critical security fixes discovered by the maintainers
• Integration of Zizmor security scanning to prevent similar issues
• This makes the update essential for security compliance

Code Quality & Best Practices ✅

• Minimal change: Single line version bump (.github/workflows/pypi-publish.yml:37)
• No breaking changes: The action maintains backward compatibility
• Standard Dependabot PR: Follows expected update patterns

Compatibility Analysis ✅

• Python 3.13 support: Action now runs on Python 3.13 (up from earlier versions)
• Dependency updates: Updated internal dependencies for better stability
• Existing workflow compatibility: No changes needed to current usage pattern
• Token-based auth: Continues to use __token__ and secrets.PYPI_PASSWORD as expected

Performance Considerations ⚡

• Improved runtime: Upgraded to Python 3.13 for better performance
• Dependency cleanup: Removed pip-with-requires-python for cleaner runtime
• No performance regressions expected: Action maintains same interface

Notable Improvements 🚀

• Attestations feature: No longer experimental (stable for a year)
• Better diagnostics: Enhanced output including GitHub Environment claims
• Hash-pinning support: Compatible with organizational policies requiring SHA-pinned actions
• Reusable workflow warnings: Better guidance for unsupported configurations

Recommendations ✅

1. Approve and merge: This is a security-critical update
2. No action required: Current workflow configuration will continue working
3. Monitor release: Watch for any issues after deployment, though none are expected
4. Consider attestations: The stable attestations feature could be enabled for additional security

Risk Assessment: LOW 🟢

• Well-tested major release with extensive backwards compatibility
• Security fixes outweigh minimal upgrade risk
• Standard PyPI publishing workflow unchanged

---