Skip to content

ci: pin actions to full-length commit SHAs - #94

Merged
DeepDiver1975 merged 1 commit into
mainfrom
ci/pin-actions-to-sha
Aug 21, 2026
Merged

ci: pin actions to full-length commit SHAs#94
DeepDiver1975 merged 1 commit into
mainfrom
ci/pin-actions-to-sha

Conversation

@DeepDiver1975

Copy link
Copy Markdown
Member

Problem

Every workflow run in this repo since 2026-08-21 07:51 UTC ends in
startup_failure with zero jobs and zero check-runs — on main, on PRs and
on Dependabot branches alike (runs
#160,
#161,
#162,
#163).
The run annotation:

The actions actions/checkout@v7, actions/setup-node@v7,
actions/upload-pages-artifact@v5, and actions/deploy-pages@v5 are not
allowed in owncloud/docs.owncloud.com because all actions must be from a
repository owned by owncloud, created by GitHub, or match one of the
patterns: …

The org Actions policy requires actions to be pinned to a full-length commit
SHA, so the movable tags are rejected before any job is created. Nothing in
this repo changed — the same file built fine on 2026-08-20 (run #158). It is
not caused by #93 either: run #160 was on an unmodified base.

Fix

Pin all four actions to the commit of the release they already tracked, with
the version in a trailing comment — the same convention as
owncloud/docs,
which pins the identical actions/checkout v7.0.1 and actions/setup-node
v7.0.0 commits and is unaffected.

action pinned to
actions/checkout 3d3c42e5aac5ba805825da76410c181273ba90b1 (v7.0.1)
actions/setup-node 820762786026740c76f36085b0efc47a31fe5020 (v7.0.0)
actions/upload-pages-artifact fc324d3547104276b827a68afc52ff2a11cc49c9 (v5.0.0)
actions/deploy-pages cd2ce8fcbc39b97be8ca5fce6e763baed58fa128 (v5.0.0)

No behaviour change — same releases, immutable refs. Dependabot's
github-actions ecosystem is already configured in .github/dependabot.yml,
so the pins keep getting bumped automatically.

Why now

This blocks
owncloud/admin#246, which brings
this repo under safe-settings and gates main on the build check. A startup
failure produces no build check-run at all, so with build required every
merge would be blocked. build must report again before that lands.

Verification

This PR's own run is the test: it must start and report build as a success
instead of startup_failure.

🤖 Generated with Claude Code

The org Actions policy requires every action to be pinned to a full-length
commit SHA. The movable tags in this workflow are rejected before any job is
created, so every run since 2026-08-21 07:51 UTC ended in `startup_failure`
with no check-runs at all — on `main`, on PRs and on Dependabot branches
alike:

    The actions actions/checkout@v7, actions/setup-node@v7,
    actions/upload-pages-artifact@v5, and actions/deploy-pages@v5 are not
    allowed in owncloud/docs.owncloud.com because all actions must be from a
    repository owned by owncloud, created by GitHub, or match one of the
    patterns: ...

Pin all four to the commit of the release they already tracked, with the
version in a trailing comment — the same convention as owncloud/docs, which
pins the identical actions/checkout v7.0.1 and actions/setup-node v7.0.0
commits and is unaffected. Dependabot's github-actions ecosystem is already
configured here, so the pins keep getting bumped.

This also unblocks gating `main` on the `build` check: a startup failure
produces no `build` check-run at all, so a required `build` context would
block every merge.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Signed-off-by: Thomas Müller <1005065+DeepDiver1975@users.noreply.github.com>
@DeepDiver1975
DeepDiver1975 merged commit d94c9f0 into main Aug 21, 2026
2 checks passed
@DeepDiver1975
DeepDiver1975 deleted the ci/pin-actions-to-sha branch August 21, 2026 08:53
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.

2 participants