Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sbomnix: Use nixpkgs from sbomnix upstream #365

Merged
merged 1 commit into from
Feb 12, 2025

Conversation

henrirosten
Copy link
Collaborator

@henrirosten henrirosten commented Feb 11, 2025

This change fixes an issue with vulnix scans, an example error is here: https://ghaf-jenkins-controller-prod.northeurope.cloudapp.azure.com/job/ghaf-nightly-pipeline/62/execution/node/385/log/.

That same issue was fixed in vulnix upstream: nix-community/vulnix#101. The vulnix fix in nixpkgs has not been backported to 24.11, which is the nixpkgs version ghaf-infra flake currently follows. Therefore, if we enforce sbomnix to follow the 24.11 nixpkgs, it will use vulnix version vulnix-1.10.1-unstable-2024-04-02 which does not include the fix.

To include the fix in ghaf-infra, we need to let sbomnix use a version of nixpkgs from nixos-unstable that includes vulnix version 1.10.2 with the fix included.

@henrirosten henrirosten force-pushed the fix-vulnix-runtime-scan branch from 025d7b9 to 68914bb Compare February 11, 2025 12:53
@henrirosten henrirosten marked this pull request as ready for review February 11, 2025 13:11
@henrirosten henrirosten requested a review from a team February 11, 2025 13:11
@henrirosten henrirosten merged commit 5764bfe into main Feb 12, 2025
6 checks passed
@henrirosten
Copy link
Collaborator Author

Deployed to prod jenkins-controller VM

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.

2 participants