Skip to content

Conversation

@sean-breen
Copy link
Contributor

@sean-breen sean-breen commented Nov 25, 2025

Proposed changes

Adds the govulncheck action to our CI workflow to catch and report vulnerabilities to the Security tab.

Also adds a nightly-scans.yml workflow to run the vulnerability scan nightly against mainn and dev-v2 branches.

Checklist

Before creating a PR, run through this checklist and mark each as complete.

  • I have read the CONTRIBUTING document
  • I have run make install-tools and have attached any dependency changes to this pull request
  • If applicable, I have added tests that prove my fix is effective or that my feature works
  • If applicable, I have checked that any relevant tests pass after adding my changes
  • If applicable, I have updated any relevant documentation (README.md)
  • If applicable, I have tested my cross-platform changes on Ubuntu 22, Redhat 8, SUSE 15 and FreeBSD 13

@codecov
Copy link

codecov bot commented Nov 25, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 86.27%. Comparing base (0472d6d) to head (73b02e8).
⚠️ Report is 5 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1416      +/-   ##
==========================================
- Coverage   86.38%   86.27%   -0.11%     
==========================================
  Files         102      102              
  Lines       12622    12622              
==========================================
- Hits        10903    10890      -13     
- Misses       1238     1253      +15     
+ Partials      481      479       -2     

see 6 files with indirect coverage changes


Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0472d6d...73b02e8. Read the comment docs.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@sean-breen sean-breen marked this pull request as ready for review November 27, 2025 11:12
@sean-breen sean-breen requested a review from a team as a code owner November 27, 2025 11:12
security-events: write
with:
target-branch: ${{ github.event.pull_request.base.ref || github.ref_name }}
go-version-input: '1.24.10'
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a way to get the golang version from the go.mod file like how we do it for the setup-go action on line 72?

uses: ./.github/workflows/vulncheck.yml
with:
target-branch: 'dev-v2'
go-version-input: '1.24.10'
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agent V2 is actually on 1.24.9 at the moment. So we need to be able to get the version from the go.mod instead of hardcoding it into the workflows

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added a check where we read the go version from the go.mod

@sean-breen sean-breen requested a review from dhurley November 27, 2025 14:49
on:
workflow_call:
inputs:
go-version-input:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can the go-version-input inputs be removed now?

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants