Skip to content

Improve our security scan actions - #1520

Open
apyrgio wants to merge 2 commits into
mainfrom
1395-composite-scan
Open

Improve our security scan actions#1520
apyrgio wants to merge 2 commits into
mainfrom
1395-composite-scan

Conversation

@apyrgio

@apyrgio apyrgio commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

The scan.yml and scan_released.yml actions share some common logic. Factor it out into separate actions, and provide the variables via inputs.

Moreover:

  1. Change a bit the scanning logic so that we scan only once, instead of scanning twice (once without failures and then with failures).
  2. Every two weeks, specifically on the 5th and 20th of each month, set the severity cutoff to High, instead of critical.

Closes #1395

(Note, this PR is repurposed from #1438, to decouple it from the changes required for the SECURITY.md file)

apyrgio added 2 commits July 13, 2026 13:28
The `scan.yml` and `scan_released.yml` actions share some common logic.
Factor it out into separate actions, and provide the variables via
inputs.

Moreover, change a bit the scanning logic so that we scan only once,
instead of scanning twice (once without failures and then with
failures).
Every two weeks, specifically on the 5th and 20th of each month, set the
severity cutoff to High, instead of critical. We use the 5th and 20th of
each month for two reasons:

1. The cron syntax does not have a way to express a "biweekly" cadence.
2. The start and end of a month tend to be "busy" times, so we skew the
   frequency a few days later.

Closes #1395
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

Improve triage workflow for CVEs

1 participant