ci(bluebuild): pin blue-build/github-action to commit SHA #6

Merged
s8n merged 1 commit from feat/a1-bluebuild-pin into v0.7-bluebuild-spike 2026-05-06 13:53:16 +01:00

1 commit

Author SHA1 Message Date
s8n-ru
4b80d06fde ci(bluebuild): pin blue-build/github-action to commit SHA
Some checks failed
Build veilor-os OCI (BlueBuild) / Build + sign + push OCI (pull_request) Failing after 12s
Lint / Kickstart syntax (pull_request) Failing after 2s
Lint / Shell scripts (pull_request) Failing after 38s
Lint / No personal/onyx leaks (pull_request) Failing after 35s
Replace @v1 with @24d146df25adc2cf579e918efe2d9bff6adea408 (the commit
v1 currently resolves to). Tag pins on third-party actions are mutable
— a maintainer or attacker can re-point v1 at a malicious commit and
silently change what runs on every push.

Trailing comment '# v1' preserves human readability for future bumps.

Refs: 9-agent CI hardening wave (agent 8), 2026-05-05.
2026-05-06 10:32:13 +01:00