rusackas opened a new pull request, #41383: URL: https://github.com/apache/superset/pull/41383
### SUMMARY The `actions/setup-python` step in our composite backend setup action (and the `bump-python-package` workflow) is pinned to commit `a309ff8b426b58ec0e2a45f0f869d46889d02405`, but the inline version comment read `# v6`. That commit actually corresponds to release tag **v6.2.0**. The floating `# v6` tag points at a different commit (`ece7cb06…`, currently v6.3.0). zizmor's `ref-version-mismatch` rule flags this because the human-readable comment misrepresents the exact pinned version, which makes audits and Dependabot bumps harder to reason about. This PR updates both occurrences of the comment to the truthful `# v6.2.0`. The pinned SHA is unchanged, so runtime behavior is identical — this is purely a documentation/accuracy fix to satisfy the supply-chain pin convention. Resolves code-scanning alert #2549. ### BEFORE/AFTER Before: ```yaml uses: actions/setup-python@a309ff8b426b58ec0e2a45f0f869d46889d02405 # v6 ``` After: ```yaml uses: actions/setup-python@a309ff8b426b58ec0e2a45f0f869d46889d02405 # v6.2.0 ``` ### TESTING INSTRUCTIONS `pre-commit run --files .github/actions/setup-backend/action.yml .github/workflows/bump-python-package.yml` passes, including the `zizmor (GHA security audit)` hook. ### ADDITIONAL INFORMATION - [ ] Has associated issue: - [ ] Required feature flags: - [ ] Changes UI - [ ] Includes DB Migration (follow approval process in [SIP-59](https://github.com/apache/superset/issues/13351)) - [ ] Migration is atomic, supports rollback & is backwards-compatible - [ ] Confirm DB migration upgrade and downgrade tested - [ ] Runtime estimates and downtime expectations provided - [ ] Introduces new feature or API - [ ] Removes existing feature or API 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
