Add workflow to re-pin actions-ext references - #184
Merged
Conversation
Dependabot cannot maintain these pins. The template workflows are .jinja files outside any .github/workflows directory, so it never scans them, and the pins point at main commits rather than tags, which is all Dependabot can resolve. Runs weekly, on demand, or on an actions-ext-updated repository_dispatch, and opens a PR when any pin has moved. Also available locally as make update-action-pins / make check-action-pins. Signed-off-by: Tim Paine <3105306+timkpaine@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
actions-extpins inside the templates drift silently because Dependabotcannot see them. The template workflows live at
python/**/.github/workflows/*.jinja— outside any real.github/workflowsdirectory and not
.yml/.yaml— so thegithub-actionsecosystem neverscans them. No Dependabot config can reach those files.
The evidence is in this repo's own history: #157 is the only Dependabot pull
request
basehas ever received, and it touched.github/workflows/build.yamland nothing else, while the same pins in the templates went stale.
Dependabot does handle the pins it can see, including SHA pins that point at
untagged
maincommits — #157 bumpedactions-ext/rust/setupbetween twosuch commits. So
.github/workflows/build.yamlis covered already; it justmoves on the monthly cadence.
This adds a script plus a workflow that resolves each
actions-extrepo'scurrent
mainand re-pins every reference,.jinjafiles included, opening aPR when anything moved.
Triggers: weekly cron,
workflow_dispatch, and anactions-ext-updatedrepository_dispatch.Locally:
Not wired up yet: the
repository_dispatchtrigger is accepted butnothing sends it. Emitting it from the
actions-extrepos on push tomainneeds a PAT there, since
GITHUB_TOKENcannot dispatch cross-repo. Until thenthe cron and manual triggers cover it.
Also note PRs opened by
GITHUB_TOKENdo not triggeron: pull_requestworkflows, so the bot's PR will not run template CI on its own.