lock: populate auto-discovered keys into the json lock file #1985
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.
Commit claude code
Export ParseAlpineVersion, instead of wrapping it
Ignore missing alpine keys when offline
Add new lock test with alpine discovery keys
lock: Perform chainguard-style key discovery
Ensure stable lock output
Populate auto-discovered keys into the expanded lock file. This helps with subsequent offline builds, plugging into existing (fixed up) caching mechanism which appears to fix all offline building issues for me on the rules_apko side.
I think this will correctly support multi-arch builds, with per-arch keys, with auto-discovered keys, actually offline for the first time properly.