chore(deps): bump vuls2 and vuls-data-update for openssh RangeType - #2643
Closed
MaineK00n wants to merge 1 commit into
Closed
chore(deps): bump vuls2 and vuls-data-update for openssh RangeType#2643MaineK00n wants to merge 1 commit into
MaineK00n wants to merge 1 commit into
Conversation
The pinned vuls-data-update knew fewer enum values than the nightly branch: cpecriterion/range.RangeType gained `openssh`, so detection would skip criteria carrying it once the nightly DB starts emitting them. Bumped upstream first, as the drift playbook requires — MaineK00n/vuls2#425 pins vuls-data-update 4b1dbcf, so pinning that vuls2 merge commit here raises the direct vuls-data-update requirement to the same version and keeps the standalone vuls2 binary and the vuls-data-db nightly build on one vocabulary. Incoming: - MaineK00n/vuls2#425 chore(deps): bump vuls-data-update for openssh security - MaineK00n/vuls-data-update#928 feat(openssh/security): add OpenSSH security advisory data source - MaineK00n/vuls-data-update#939 fix(extract/apple): bound 10.x in-line updates below by their own line `print-enums` for the new pin against 4b1dbcf diffs empty. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Collaborator
Author
|
Superseded by #2636, which landed the same pins (vuls2 |
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
1 participant
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.
Fixes #2642
What
Bumps the vuls2 / vuls-data-update pins so the enum vocabulary matches the vuls-data-update nightly branch again:
github.com/MaineK00n/vuls27a8b91a51f44→ab3a3111c7f1github.com/MaineK00n/vuls-data-update305a95f8ba56→4b1dbcf513ffThe drift the scheduled
check-enumsrun reported was a single new value:> pkg/extract/types/data/detection/condition/criteria/criterion/cpecriterion/range.RangeType opensshBumped upstream first, per the playbook in the issue: MaineK00n/vuls2#425 already pins vuls-data-update
4b1dbcf, so pinning that vuls2 nightly merge commit here raises the direct vuls-data-update requirement to the same version through module graph resolution. That keeps this repo, the standalone vuls2 binary, and the vulsio/vuls-data-db nightly build on one vocabulary — bumping vuls-data-update here alone would leave the binary that builds the DB skipping data carrying the new range type.Incoming
vuls2 (
7a8b91a51f44...ab3a3111c7f1):vuls-data-update (
305a95f8ba56...4b1dbcf513ff):Verification
GOEXPERIMENT=jsonv2 go run github.com/MaineK00n/vuls-data-update/tools/print-enumsfor the new pin vs...@4b1dbcf513ff1522de398d087c29e44a9c5a38bf— diff is empty (143 lines each).go build ./...andgo test ./...pass (with theintegrationsubmodule checked out).Converting the new source's detection results into vuls0 report models (CveContentType, confidences, advisory links) is separate follow-up work; this PR only realigns the pins so the values stop being dropped.