Autobump nvidia vers on a schedule#183
Merged
Merged
Conversation
bleggett
force-pushed
the
bleggett/autogen-nvidia-ver
branch
from
0712985 to
240fbd4
Compare
bleggett
changed the title
tycho
approved these changes
May 21, 2026
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.
This just scrapes https://www.nvidia.com/en-us/drivers/unix/ on a weekly basis, and creates a PR with the proposed nvidia bumps for a human to merge, whenever they feel like it.
Ex. of a PR autocreated by this: #184
I need to consult with @jedsalazar to get a proper token so we aren't reliant on GH_TOKEN, otherwise the auto-created PRs won't run CI jobs on the autocreated PR without human intervention, but everything will work without that, so that can be a followup.