Skip to content

ci: add govulncheck job - #5383

Merged
kolyshkin merged 1 commit into
opencontainers:mainfrom
kolyshkin:govulncheck
Aug 11, 2026
Merged

ci: add govulncheck job#5383
kolyshkin merged 1 commit into
opencontainers:mainfrom
kolyshkin:govulncheck

Conversation

@kolyshkin

Copy link
Copy Markdown
Contributor

This is to ensure our minimal dependencies do not have known vulnerabilities.

NOTES:

  • govulncheck is not and will not be included into golangci-lint, thus a separate job.
  • we do not specify Go version to be used here to avoid reporting vulnerabilities in stdlib which we're not interested in here;
  • this is semi-useless for main branch as our dependencies are kept updated by dependabot. This makes more sense for release-* branches in which we don't routinely bump go deps.

This is to ensure our minimal dependencies do not have known
vulnerabilities.

NOTE we do not specify Go version to be used here to avoid reporting
vulnerabilities in stdlib which we're not interested in here.

Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
@kolyshkin kolyshkin added area/ci backport/1.4-todo A PR in main branch which needs to backported to release-1.4 backport/1.5-todo A PR in main branch which needs to be backported to release-1.5 labels Aug 5, 2026
@kolyshkin

Copy link
Copy Markdown
Contributor Author

Similar to opencontainers/cgroups#15 (see some discussions in there).

@thaJeztah thaJeztah left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

LGTM

probably should be cherry-picked to the release branches.

@thaJeztah

Copy link
Copy Markdown
Member

probably should be cherry-picked to the release branches.

LOL and you already added labels for that 😅

@rata rata left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

LGTM. We can't put this to run on a release branch only, I guess? (like some checks that can run on certain branches and so)

@kolyshkin

Copy link
Copy Markdown
Contributor Author

LGTM. We can't put this to run on a release branch only, I guess? (like some checks that can run on certain branches and so)

We actually run CI a few times a week on release branches (from https://github.com/opencontainers/runc/blob/main/.github/workflows/scheduled.yml); the problem is the results are not very visible* (they can only be seen in https://github.com/opencontainers/runc/actions, and you have to scroll down or search).

*We even missed adding release-1.4 and 1.5 to that file; opened #5393 to fix.

@kolyshkin
kolyshkin merged commit 7495fae into opencontainers:main Aug 11, 2026
56 checks passed
@kolyshkin kolyshkin added backport/1.5-done A PR in main branch which has been backported to release-1.5 backport/1.4-done A PR in main branch which has been backported to release-1.4 and removed backport/1.4-todo A PR in main branch which needs to backported to release-1.4 backport/1.5-todo A PR in main branch which needs to be backported to release-1.5 labels Aug 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/ci backport/1.4-done A PR in main branch which has been backported to release-1.4 backport/1.5-done A PR in main branch which has been backported to release-1.5

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants