Skip to content

fix(ci): pin GitHub Actions to commit SHAs (#15030) - #15035

Closed
hf-security-analysis[bot] wants to merge 0 commit into
up-pythonfrom
security/workflow-hardening/pr-15030-pins
Closed

hf-security-analysis[bot] wants to merge 0 commit into
up-pythonfrom
security/workflow-hardening/pr-15030-pins

Conversation

@hf-security-analysis

@hf-security-analysis hf-security-analysis Bot commented Oct 14, 2026 •

Copy link
Copy Markdown
Contributor

Automated hardening of the workflow files flagged on #15030: action pins only.

Each kind of fix has its own pull request, from a security/workflow-hardening/pr-15030-* branch, and any of them can be merged first: the others are rebuilt on top when this one lands.

Targets up-python. Files changed, and what changed them:

  • .github/workflows/build_pr_documentation.yml — action pins

Fixed by this PR:

  • HIGH unpinned-action (pinact) — .github/workflows/build_pr_documentation.yml:28

This does not fix everything. 1 further finding(s) (1 high) need a decision this bot should not make for you. They are in the security channel with their locations — deliberately not repeated here, since this repository may be public and they are not fixed yet.

Pins come from pinact and are mechanical: each SHA is the commit the tag already resolves to.

@github-actions github-actions Bot added CI size/S PR with diff < 50 LOC labels Oct 14, 2026
@hf-security-analysis
hf-security-analysis Bot force-pushed the security/workflow-hardening/pr-15030-pins branch from 22404eb to 5622c68 Compare October 14, 2026 12:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CI size/S PR with diff < 50 LOC

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants