Revert beego bump in harbor-2.11 #26370
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
|
You need to bump the epoch as well |
|
Just to add, unfortunately I don't believe there's a way. I filed advisories but automation still tries to remediate the CVE |
|
and |
Signed-off-by: RJ Trujillo <[email protected]>
|
Sounds good, will keep an eye out for the automation PR and put it in draft. Thank you @ajayk & @EyeCantCU! |
ajayk
approved these changes
Aug 15, 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.
@EyeCantCU reverted this in #26137 but then our automation added it back in (#26157). I think it's breaking the harbor helm test which is causing https://github.com/chainguard-dev/image-release-stats/issues/280 (cc @smoser)
I added
manual: truefor now but please let me know if there's a better way to stop automation from adding this back in