-
Notifications
You must be signed in to change notification settings - Fork 341
Pins in actions-lock.json can drift out of sync with workflow #22785
Copy link
Copy link
Open
Labels
enhancementNew feature or requestNew feature or request
Description
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
- key the pins in actions-lock.json by workflow or
- 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).
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or request
Type
Fields
Give feedbackNo fields configured for issues without a type.