Expose ignoreSignatures functionality #1375
Merged
Conversation
This file contains 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
Signed-off-by: Kevin-Molina <kevin.molina@csu.fullerton.edu>
imjasonh
approved these changes
Jul 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Melange Pull Request Template
Expose ignoreSignatures functionality from apko to melange CLI clients.
Follow up for this PR: chainguard-dev/apko#1179
Functional Changes
Notes: I've run the full test suite locally without issue, but do not see wolfi as an E2E test case, so leaving this unchecked as unable to verify.
SCA Changes
Notes: E2E test suite passes. Was also able to build an custom APK locally without issues.
Linter
Notes: Linter checks passed locally as well