You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Will Dependabot's updates to the generated file (~.lock.yml) work? #19194
Status (2026-10-07; Maintainer direction): On March 3, a maintainer invited a strategy for handling Dependabot edits to generated .lock.yml files and noted that the GitHub Actions token cannot edit those files. The next step is to propose a maintenance approach that accounts for that constraint and keeps generated files in sync.
Current-state refresher (2026-10-16): the original question is now documented and compiler-managed pins have protection; generated edits are still not a durable source of truth. The compilation reference explicitly says not to merge Dependabot bumps of github/gh-aw-actions pins: the compiler coordinates those pins. gh aw compile reconciles a managed ignore rule when an existing GitHub Actions update block is present, including action subpaths after merged #54812.
The Dependabot reference documents that rule and the source-first update/recompile flow. This does not mean every dependency in every generated lock file is ignored or that arbitrary Dependabot changes are imported back into workflow Markdown; recompilation can still overwrite generated-only edits.
Thus the usage question has a concrete answer, while broader automated maintenance can remain follow-up work. This is a documentation/source assessment, not a Dependabot execution test; no workflow files, labels or issue state were changed.
Closing as completed: the original usage/ownership question is answered (2026-10-22). Dependabot-only edits to generated .lock.yml are not a durable update path: recompilation can overwrite them. The current compilation reference explicitly says not to merge Dependabot-only bumps of compiler-owned github/gh-aw-actions pins and documents regeneration via gh aw compile / gh aw update-actions instead.
The Dependabot reference and reconciler establish the managed <actions-repository>/* ignore rule when an existing GitHub Actions update block is present; merged #54812 fixed sub-action matching. This is not a blanket ignore for every dependency or every generated file, nor does it import arbitrary generated edits back into source. Source-owned runtime dependencies should be updated in workflow Markdown and recompiled (documented flow).
That resolves the question asked here without claiming a complete automated maintenance system. GitHub-native .github/workflows/actions.lock emission is a separate, still-open feature in #70264; this closure does not mark it implemented or duplicate it. This conclusion is based on current source/docs, not a live Dependabot execution test.
Activity
pelikhan commentedon Mar 2, 2026
It will be erased by the next compile. Best to run
pelikhan commentedon Mar 3, 2026
Working on maintenance actions to help with this.
lfgcampos commentedon Mar 3, 2026
Thank you!
Happy to provide a PR too, if that is possible in any way
pelikhan commentedon Mar 3, 2026
You can provide an issue with a strategy to handle it. The challenge is that the github actions token cannot edit those files...
pelikhan commentedon Mar 15, 2026
What did you have in mind for maintenance actions?
pelikhan commentedon Oct 7, 2026
Status (2026-10-07; Maintainer direction): On March 3, a maintainer invited a strategy for handling Dependabot edits to generated
.lock.ymlfiles and noted that the GitHub Actions token cannot edit those files. The next step is to propose a maintenance approach that accounts for that constraint and keeps generated files in sync.pelikhan commentedon Oct 16, 2026
Current-state refresher (2026-10-16): the original question is now documented and compiler-managed pins have protection; generated edits are still not a durable source of truth. The compilation reference explicitly says not to merge Dependabot bumps of
github/gh-aw-actionspins: the compiler coordinates those pins.gh aw compilereconciles a managed ignore rule when an existing GitHub Actions update block is present, including action subpaths after merged #54812.The Dependabot reference documents that rule and the source-first update/recompile flow. This does not mean every dependency in every generated lock file is ignored or that arbitrary Dependabot changes are imported back into workflow Markdown; recompilation can still overwrite generated-only edits.
Thus the usage question has a concrete answer, while broader automated maintenance can remain follow-up work. This is a documentation/source assessment, not a Dependabot execution test; no workflow files, labels or issue state were changed.
pelikhan commentedon Oct 22, 2026
Closing as completed: the original usage/ownership question is answered (2026-10-22). Dependabot-only edits to generated
.lock.ymlare not a durable update path: recompilation can overwrite them. The current compilation reference explicitly says not to merge Dependabot-only bumps of compiler-ownedgithub/gh-aw-actionspins and documents regeneration viagh aw compile/gh aw update-actionsinstead.The Dependabot reference and reconciler establish the managed
<actions-repository>/*ignore rule when an existing GitHub Actions update block is present; merged #54812 fixed sub-action matching. This is not a blanket ignore for every dependency or every generated file, nor does it import arbitrary generated edits back into source. Source-owned runtime dependencies should be updated in workflow Markdown and recompiled (documented flow).That resolves the question asked here without claiming a complete automated maintenance system. GitHub-native
.github/workflows/actions.lockemission is a separate, still-open feature in #70264; this closure does not mark it implemented or duplicate it. This conclusion is based on current source/docs, not a live Dependabot execution test.