chore: Pin OSV Go dependencies to stable pseudo-version#294
Open
jess-lowe wants to merge 1 commit into
Open
Conversation
Member
|
I'm assuming dependabot will not catch these as new versions are released. Is there another way for this repo to be notified when there are new versions to use? Or could we make it part of the release flow to update the pin here? |
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
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.
Due to this project's workflow fetching the osv vulnfeeds master branch directly, the GitHub actions relying on the OSV code broke the CI for a while.
Now that that is all fixed, in order to prevent this from happening again, I've updated the workflow to stop tracking master.
This PR points directly to the newly isolated /external directory and pins it to a specific, stable Go pseudo-version.