rusackas opened a new pull request, #42038: URL: https://github.com/apache/superset/pull/42038
### SUMMARY The `actions/setup-node` action is pinned by SHA `48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e` across a dozen workflow files, but the trailing comment reads `# v6`. That SHA actually corresponds to tag **v6.4.0** (confirmed via `gh api repos/actions/setup-node/tags`); the floating `v6` tag has since moved to a newer release (`249970729cb0...`). The comment therefore misrepresents the pinned version, which is exactly what zizmor's `ref-version-mismatch` audit flags. This updates the comment to the truthful version (`# v6.4.0`) in every file so it matches the pinned commit. **No SHA change** — runtime behavior is identical. This matches the format already used correctly in `.github/workflows/github-action-validator.yml`, and follows the same fix pattern established in #41160, #41383, and #41482 for other actions. Affected files (one line each, two occurrences in `tag-release.yml` and `superset-e2e.yml`/`superset-docs-verify.yml`): - `.github/workflows/embedded-sdk-release.yml` - `.github/workflows/embedded-sdk-test.yml` - `.github/workflows/pre-commit.yml` - `.github/workflows/release.yml` - `.github/workflows/scheduled-docker-image-refresh.yml` - `.github/workflows/superset-docs-deploy.yml` - `.github/workflows/superset-docs-verify.yml` - `.github/workflows/superset-e2e.yml` - `.github/workflows/superset-playwright.yml` - `.github/workflows/superset-translations.yml` - `.github/workflows/tag-release.yml` - `.github/workflows/tech-debt.yml` Resolves code-scanning alert #2581 (zizmor `ref-version-mismatch`), and the 14 other open alerts filed against the same underlying pin: #2568, #2569, #2570, #2571, #2572, #2573, #2574, #2575, #2576, #2577, #2578, #2579, #2580, #2582. ### BEFORE/AFTER Before: `uses: actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e # v6` After: `uses: actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e # v6.4.0` ### TESTING INSTRUCTIONS `pre-commit run --files <all files listed above>` — the `zizmor (GHA security audit)` hook passes, and a direct `zizmor --no-exit-codes` run over the changed files reports zero `ref-version-mismatch` findings for `actions/setup-node`. The pinned SHA is byte-for-byte unchanged, so action behavior is unaffected. ### 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]
