fix: eef yaml config #4267
Merged
fix: eef yaml config #4267
Conversation
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
jess-lowe
pushed a commit
that referenced
this pull request
Oct 31, 2025
Follow up to #4192 & #4267 The link only existed with the CVE ID in it and not the OSV ID. I created a redirect at the given path. I've verified a few test cases manually, but still can't see any info on `https://api.test.osv.dev/v1experimental/importfindings/eef`.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
We didn't catch this when merging:
linkwas 404-ing, since it's expecting the prefix of the path to the OSV recordhuman_linkwas usingCVE_IDinstead ofBUG_ID