ci: push auto-built dist via deploy key (enables runtime-dep auto-merge)#91
Merged
Conversation
Pushing the rebuilt dist/ with GITHUB_TOKEN does not start new workflow runs, so the required checks never re-run on the new commit and native auto-merge stalls on runtime-dependency PRs that change dist/. Push with the dist-auto-build deploy key instead, which re-triggers CI and lets auto-merge complete.
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.
Why
Dev-dependency PRs auto-merge fine because they don't change
dist/. Runtime-dependency PRs (axios, etc.) do changedist/:check-distrebuilds it and commits to the PR branch, but that commit is pushed withGITHUB_TOKEN, which does not start new workflow runs. So the required checks (JavaScript Tests,GitHub Actions Test) never re-run on the new head, branch protection keeps blocking, and native auto-merge stalls.Change
check-distnow pushes the rebuiltdist/using a dedicateddist-auto-builddeploy key (private key in theDIST_DEPLOY_KEYActions + Dependabot secret) instead ofGITHUB_TOKEN. A deploy-key push re-triggers CI on the new commit, the required checks pass on the new head, and auto-merge completes —dist/and the dependency bump land together.The key is referenced only by the push step (not during
npm ci/build), and only runs on source branches (never protectedmain).Notes
dist/commit re-runscheck-dist, which findsdist/already in sync → no further commit.