Skip to content

Pins in actions-lock.json can drift out of sync with workflow #22785

@dsyme

Description

@dsyme

If I have two workflows

.github/workflows/a.md
.github/workflows/b.md

and run

gh aw compile .github/workflows/a.md

then the action pins for "b.md" can currently go out of sync.

Suggestion is to either

  1. key the pins in actions-lock.json by workflow or
  2. store the pins in the .lock.yml

One idea is the actions-lock.json can be leveraged by dependabot down the road. But to do that the information must be reliable and kept in sync.

There's a slight difference of POV on this file, because are individual workflows "isolated" from each other or part of an "overall project", e.g. cooperating with each other.

  • If workflows are isolated from each pther that would imply putting the pins in the .lock.yml, or at least keying the pins
  • If workflows form a unfiied project then that would imply putting them in actions-lock.json and not allowing selective recompilation

My vote is that automations are isolated from each other (and so may be compiled with different versions of gh-aw).

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions