fix: pin pypa/gh-action-pypi-publish to a commit SHA

[irfanuddinahmad]

Summary

Pin pypa/gh-action-pypi-publish to a commit SHA (was @release/v1, a floating branch ref), consistent with how every other action in this workflow is already pinned.

Why

This repo's own dedicated SHA-pinning PR (#53) pinned actions/checkout, python-semantic-release/python-semantic-release, python-semantic-release/publish-action, actions/upload-artifact, actions/download-artifact, and actions/setup-node in this same file -- but missed pypa/gh-action-pypi-publish@release/v1. My guess: every other line used a normal @vX version tag, which whatever tool/regex drove that sweep would recognize; release/v1 looks like a branch name rather than that pattern, so it slipped through.

This isn't just a consistency nit. openedx/xblocks-core's real release just failed with docker: manifest unknown because @release/v1 resolved to a commit whose Docker image wasn't published on ghcr.io yet (a race between the branch moving and the image being built) -- see https://github.com/openedx/xblocks-core/actions/runs/29327012856/job/87066591905.

Since this repo is the reference implementation the org-wide "modernize Python tooling" effort copies from (openedx/public-engineering#506), the unpinned ref propagates into every downstream repo that follows this template -- it already did into several of the repos in that effort before this was caught.

For what it's worth, pypa/gh-action-pypi-publish's own README shows @release/v1 in its usage examples, but the same README's "pro tip" note recommends pinning to a tag or SHA rather than a branch pointer -- there's no upstream guidance suggesting this action is meant to be exempt from normal pinning practice.

Test plan

• YAML is unchanged apart from the two uses: lines; no functional change to the workflow's logic.
• SHA cef221092ed1bacb1cc03d23a2d87d1d172e277b is the current tip of pypa/gh-action-pypi-publish's release/v1 branch (v1.14.0) as of this PR.

🤖 Generated with Claude Code

[openedx-webhooks]

Thanks for the pull request, @irfanuddinahmad!

This repository is currently maintained by @feanil.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

Details

---

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.04%. Comparing base (00aa944) to head (21f4c9e).

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #54   +/-   ##
=======================================
  Coverage   93.04%   93.04%           
=======================================
  Files          16       16           
  Lines         503      503           
  Branches       18       18           
=======================================
  Hits          468      468           
  Misses         24       24           
  Partials       11       11           

Flag	Coverage Δ
unittests	93.04% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.