Skip to content

Show each driver's branch and build branch (#7) - #8

Merged
indep-arg merged 2 commits into
mainfrom
7-adding-the-corresponding-development-branch-number-fork-to-the-driver-number
Oct 11, 2026
Merged

indep-arg merged 2 commits into
mainfrom
7-adding-the-corresponding-development-branch-number-fork-to-the-driver-number

Conversation

@indep-arg

Copy link
Copy Markdown
Owner

Closes #7.

Adds two optional fields to every driver, both filled for all 90 drivers from official NVIDIA files:

  • branch: the release branch from the header of each release notes PDF. "Release 615 Driver for Windows, Version 617.42" is R615.
  • build_branch: the build branch stored in the driver itself, in Display.Driver/nvlddmkm.sys inside each official installer, right after the version ("617.42 ... r617_07-22 ... RELEASE").

On the site

  • Driver pages and the latest driver show both next to the channel, with the build branch in its own color.
  • The drivers table has a Branch column. Search finds a release branch (R615) or a build branch (r617_07 or r617_07-22).
  • Bug pages show both for every driver the bug appears in, and how many branches it spans.
  • Methodology explains where each value comes from.

One release branch holds several build branches, and a driver sometimes comes from an older build branch than the one before it. For example, 531.61 and 531.79 were built from r530_00, after 531.41 came from r531_37.

New optional branch field, filled for all 90 drivers from the header of
each release notes PDF ("Release 615 Driver for Windows, Version 617.42"
is R615). The validator checks its format and that a branch isn't newer
than the version.

Driver pages and the latest driver show the branch next to the channel,
the drivers table has a branch column and search finds a branch by its
name (R615). Bug pages list the branch of every driver the bug appears
in, and say when it spans more than one. Methodology explains where the
branch comes from.

Requested in #7.
New optional fields, filled for all 90 drivers:

- branch, from the header of each release notes PDF ("Release 615
  Driver for Windows, Version 617.42" is R615)
- build_branch

The validator checks both formats and that they fit the version.
Driver pages and the latest driver show both next to the channel, the
build branch in its own color. The drivers table has a branch column and
search finds a branch (R615) or a build branch (r617_07, r617_07-22).
Bug pages list both for every driver the bug appears in, and say how
many branches it spans. Methodology explains where each comes from.
@indep-arg indep-arg self-assigned this Oct 11, 2026
@indep-arg
indep-arg merged commit 77ef15e into main Oct 11, 2026
2 checks passed
@indep-arg
indep-arg deleted the 7-adding-the-corresponding-development-branch-number-fork-to-the-driver-number branch October 13, 2026 00:32
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.

Adding the corresponding development branch number (fork) to the driver number.

1 participant