ci: rebuild bundles for Dependabot npm updates - #100
Merged
Merged
Conversation
Signed-off-by: Rui Chen <[email protected]>
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.
Summary
Dependabot npm updates change the dependency manifests without rebuilding the checked-in action bundle, leaving PRs such as #99 failing the generated-files check.
Upload the rebuilt bundle from read-only CI, then use a separate workflow to commit only
dist/index.jsonto eligible Dependabot PRs and dispatch fresh CI. The updater checks the author, repository, changed paths, artifact, and current head; the commit rejects concurrent head changes. No PR code runs in the write-enabled job.Notes
The updater becomes active after this PR merges. It uses
GITHUB_TOKENand needs no additional secrets. The existing generated-files check stays enabled.