Repository navigation
Rebuild on a fixable CVE of any severity - #111
Merged
Merged
Conversation
|
|
||
| on: | ||
| schedule: | ||
| # ~22h ahead of the secops Wednesday 06:00 UTC scan, so anything cleared here is never filed. |
Contributor
Author
There was a problem hiding this comment.
Removed this comment since we scan daily now in secops repo
carole-lavillonniere
marked this pull request as ready for review
October 21, 2026 12:16
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.
COSY-1075
The secops scan now tracks CVEs of every severity (localstack/secops#146), so this PR makes the weekly security rebuild act on a fixable MEDIUM, LOW or UNKNOWN CVE too, instead of HIGH and CRITICAL only. Both scans drop
severityand keepignore-unfixed, so an unfixable advisory still can't trigger a rebuild every week.