Skip to content

ci: pin and align official GitHub Actions across 4FusionLab - #11

Merged
DiegoV71 merged 1 commit into
mainfrom
ci/pin-first-party-actions-20261107
Nov 7, 2026
Merged

DiegoV71 merged 1 commit into
mainfrom
ci/pin-first-party-actions-20261107

Conversation

@DiegoV71

@DiegoV71 DiegoV71 commented Nov 7, 2026

Copy link
Copy Markdown
Contributor

Summary

Bring checkout, setup-python and upload-artifact to the same commit-pinned versions used by the organization's shared platform.

First-party Actions are pinned to full SHA, verified against their upstream Git tags at the time of rollout:

  • actions/checkout → 3d3c42e5aac5ba805825da76410c181273ba90b1 (v7.0.1)
  • actions/setup-python → 6d4fd22b20465ccc0f7354476588e8df7c9ca0e0 (v7.1.0)
  • actions/setup-node → 249970729cb0ef3589644e2896645e5dc5ba9c38 (v6)
  • actions/upload-artifact → cf430e030ddbb5b0abf93d22962f4752f3646cd9 (v7.0.2)
  • actions/download-artifact → 9000827ccba6bdab643e8b6fd33ac0654aef8333 (v8.0.2)
  • Pages actions preserve their compatible major versions but are full-SHA pinned.

Safety

  • Only existing .github/workflows/*.yml files change. No runtime/package inputs change, so this merge must not create a GitHub Release.
  • GitVersion 6.8.2, shared 4FusionLab platform SHA, runtime allowlist, release triggers, build/test commands, and artifact naming stay untouched.
  • No manual tags or dispatch of a release. Merge only with green project PR checks; confirm the post-merge release job is skipped.
  • Manual Pages workflow remains manual and is not deployed by this PR.

@DiegoV71
DiegoV71 merged commit 54c0f5f into main Nov 7, 2026
7 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