Add parser for GitHub Actions lockfile (actions.lock) - #51
Draft
andrew wants to merge 1 commit into
Draft
Conversation
Registers .github/workflows/actions.lock as a github-actions lockfile. The format is written by gh actions-lock and defined at github/actions-lockfile; it is pre-1.0 so the parser is deliberately lenient (unknown fields ignored, no version gate). Each dependencies: entry becomes one row with Name from the pin key, Version from the ref: field, Integrity from commit:, and Direct set for pins referenced from a workflows: list.
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.
Registers
.github/workflows/actions.lockas agithub-actionslockfile. The file is written bygh actions-lockand the schema is defined in github/actions-lockfile.The format is pre-1.0 and marked as subject to change, so the parser is a plain
yaml.Unmarshalthat ignores unknown fields and doesn't gate on theversion:string. That keeps older git-pkgs binaries working across schema bumps and lets us support multiple format versions later without an external dependency.Each
dependencies:entry becomes one row:Namefrom theowner/repoprefix of the pin key,Versionfromref:,Integrityfromcommit:(sha1-<hex>), andDirectset for pins that appear in aworkflows:list (transitive-only entries reached viauses:are indirect).Draft until the format is announced.