Fixing opa CVE-2025-46569 update tag version 0.69.0 to 1.4.0 #6407
Conversation
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
2 participants
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.
Pull Request Submission Checklist
are release-note ready, emphasizing
what was changed, not how.
What does this PR do?
While using snyk-alpine latest CLI causing OPA version issue showing High vulnerable as per the CVE-2025-46569 recommendation updated version changes from v0.69.0 to v1.4.0 . Because of this issue one of the production release got effected.
What does this PR do?
While using synk-alpine latest CLI causing OPA version issue showing High vulnerable CVE-2025-46569 as per the recommendation updated version changes from v0.69.0 to v1.4.0 . Because of this issue one of the production release got effected.