Software 45243 Published by

Mesa 26.3.1 just shipped as the first point release of the 26.3 branch, a bugfix-only build Dylan Baker tagged from the mesa-announce mailing list. It trims a feature-heavy cycle down to roughly 193 commits from 61 authors, cleaning up the fallout left by the 26.3.0 feature release. Most of the work concentrated in three areas: the Intel "Jay" shader compiler, the dzn Vulkan-over-D3D12 driver for Windows and WSL2, and correctness fixes for AMD's RADV.



Mesa 26.3.1 ships the first point release of the 26.3 branch

Mesa 26.3.1 has arrived as the first point release of the 26.3 branch, a bugfix-only build that prunes a feature-heavy cycle down to roughly 200 commits.

Mesa 26.3.1 is out. Dylan Baker, Mesa's release manager for years, posted the announcement on the mesa-announce mailing list. It's the first point release in the 26.3 branch, with about 193 commits coming from 61 authors. As of right now, that makes it the freshest stabilization update in the current feature line.

Point releases rarely make headlines, and that's fine. They don't ship a new Vulkan version or suddenly support a GPU you can only get by driving two hours to a specialty store. Their entire job is to mop up the mess a feature release leaves behind: the regressions, the crashes, the edge cases that looked fine in a changelog but broke on real hardware. That's the 26.3.1 story in a single sentence.

Screenshot_from_2026_07_01_17_13_56

What a point release actually is (and what it isn't)

Mesa runs on a roughly three-month release cycle, though the spacing has some give. Feature releases like 26.3.0 land new APIs, extensions, GPU support, and performance work. They're development releases, and the project openly treats them as such. Point releases like 26.3.1 follow about two weeks later, and they carry bug fixes only, backported from the feature branch.

The version number makes all of this legible. In 26.3.1 the middle digit stays fixed across the whole feature line; only the last digit ticks up. So you get 26.3.0, then 26.3.1, then 26.3.2 and beyond. Stability-focused users and distro maintainers should be running these.

Because it's a point release, 26.3.1 adds no headline features. Those already arrived with 26.3.0, tagged on 9 November 2026 as the Q4 2026 feature release. 26.3.1 exists to clean up the fallout, regressions, crashes, compatibility bugs exposed by 26.3.0, plus ordinary maintenance across every driver. For any story, that split matters. The features are a 26.3.0 story. The stabilization is the 26.3.1 story.

Baker's post singled out three areas where the work concentrated: the Intel "Jay" shader compiler, the dzn driver for Windows, and RADV, AMD's Vulkan driver. He was quick to say that list wasn't exhaustive. Nearly 200 patches landed across the rest of the codebase, and he teased that he'd see everyone again in two weeks for 26.3.2.

Checking your current version

To see what you're running, print your OpenGL driver:

glxinfo -B | grep "OpenGL version"

You're looking for something like this:

OpenGL version string: 4.6 (Compatibility Profile) Mesa 26.3.1

For Vulkan, check the driver identity instead:

vulkaninfo --summary | grep driverInfo

Building from the source tarball

If you're compiling from source, the tarball sits on mesa.freedesktop.org as mesa-26.3.1.tar.xz. The git tag is mesa-26.3.1, and the checksum is:

4e4e438eac7b840a9383988cbb7c08dad8041da544b9319fc26d319fa7348961

Verify that sum before installing anything. The PGP signature sits alongside the tarball as a .sig file.

Head here to the release announcement for a detailed change log.