@@ -173,12 +173,17 @@ whose immutable action metadata selects `node24`. The semantic
173173checker rejects any other pin so the workflow cannot silently regress to the
174174deprecated Node 20 runtime.
175175
176- The direct PyPI publisher v1.14.1 is pinned to the reviewed commit. Its only
177- action-definition change from the previously reviewed publisher is the
178- conditional ` setup-python ` fallback moving from Node 20 to Node 24; the
176+ The direct PyPI publisher v1.14.3 is pinned to
177+ ` 7245906fb61fa33a13554f9d5fb856fe61758086 ` . The reviewed
178+ [ upstream comparison] ( https://github.com/pypa/gh-action-pypi-publish/compare/ba38be9e461d3875417946c167d0b5f3d385a247...7245906fb61fa33a13554f9d5fb856fe61758086 )
179+ retains the composite action definition and Node 24 ` setup-python ` fallback.
180+ Its runtime updates include Twine, Sigstore, and certifi plus hashed dependency
181+ constraints. The certifi and Sigstore update addresses
182+ [ GHSA-5xjx -3w67-w9x9] ( https://github.com/pypa/gh-action-pypi-publish/security/advisories/GHSA-5xjx-3w67-w9x9 ) .
183+ The semantic checker requires this exact publisher SHA while preserving the
179184top-level ` publish.yml ` , ` publish ` job, ` pypi ` environment, and Trusted
180- Publisher identity remain unchanged. The semantic checker requires this exact
181- publisher SHA .
185+ Publisher identity. Local CI does not exercise OIDC publication or attestations;
186+ those require the separately authorized release workflow .
182187
183188The job invokes the pinned action release-only first with
184189` skip-github-pull-request: true ` . That step cannot continue on error and is
0 commit comments