Skip to content

Will Dependabot's updates to the generated file (~.lock.yml) work? #19194

Closed

Description

@lfgcampos

I found out that dependabot can update the generated ~.lock.yml files, bumping dependencies (usually github action versions).

Will that work or should this be flagged within the dependabot team to ignore those files?

Activity

  1. locked and limited conversation to collaborators on Mar 2, 2026
  2. unlocked this conversation on Mar 2, 2026
  3. pelikhan commented on Mar 2, 2026

    @pelikhan
    Collaborator

    It will be erased by the next compile. Best to run

     gh aw update
    
  4. pelikhan commented on Mar 3, 2026

    @pelikhan
    Collaborator

    Working on maintenance actions to help with this.

  5. lfgcampos commented on Mar 3, 2026

    @lfgcampos
    Author

    Working on maintenance actions to help with this.

    Thank you!

    Happy to provide a PR too, if that is possible in any way

  6. pelikhan commented on Mar 3, 2026

    @pelikhan
    Collaborator

    You can provide an issue with a strategy to handle it. The challenge is that the github actions token cannot edit those files...

  7. locked and limited conversation to collaborators on Mar 3, 2026
  8. unlocked this conversation on Mar 3, 2026
  9. pelikhan commented on Mar 15, 2026

    @pelikhan
    Collaborator

    What did you have in mind for maintenance actions?

  10. pelikhan commented on Oct 7, 2026

    @pelikhan
    Collaborator

    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.

  11. pelikhan commented on Oct 16, 2026

    @pelikhan
    Collaborator

    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.

  12. pelikhan commented on Oct 22, 2026

    @pelikhan
    Collaborator

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions