Skip to content

fix(ci): pin upload-pages-artifact v5 so org SHA policy allows Pages - #93

Merged
FabioLeitao merged 1 commit into
mainfrom
fix/pages-deploy-transitive-sha-pin
Sep 21, 2026
Merged

FabioLeitao merged 1 commit into
mainfrom
fix/pages-deploy-transitive-sha-pin

Conversation

@FabioLeitao

@FabioLeitao FabioLeitao commented Sep 21, 2026 •

Copy link
Copy Markdown
Contributor

Summary

  • Org sha_pinning_required blocked transitive actions/upload-artifact@v4 inside upload-pages-artifact v3.0.1 (56afc609…) even though our workflow pin was already a full SHA. That predates feat(site): publish RFC 9116 security.txt on GitHub Pages #92 (failed deploys since ~2026-08-24).
  • Bump to actions/upload-pages-artifact@fc324d3547104276b827a68afc52ff2a11cc49c9 (v5.0.0), which pins upload-artifact@bbbca2dd… (v7.0.0, JS action).
  • include-hidden-files: true so .well-known/security.txt from feat(site): publish RFC 9116 security.txt on GitHub Pages #92 is in the tarball (v5 still excludes .git / .github).
  • Guardrail test rejects the v3.0.1 SHA.

After merge, re-run Deploy GitHub Pages (push to main should fire) and confirm https://databoar.com.br/.well-known/security.txt and /security.txt.

Test plan

  • bash scripts/check-all.sh green on this branch
  • CI guardrails on this PR
  • Pages deploy green on main
  • Live GET of RFC 9116 paths on databoar.com.br

v3.0.1 called upload-artifact@v4 unpinned, so org sha_pinning_required
blocked deploys even though the workflow itself was SHA-pinned.
@FabioLeitao
FabioLeitao merged commit 1240cd9 into main Sep 21, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant