vendor: bump DirectX-Headers v1.619.1 and mesa 24.0.1#1453
Open
benhillis wants to merge 2 commits into
Open
Conversation
Updates the recommended dev-clone tag in CONTRIBUTING.md to match the
new CI default ('v1.619.1' in wslg-build's pipeline-shared.yml,
wslg-github-buddy.yml and wslg-github-release.yml). vendor/ itself is
.gitignored, so this is the only path by which a wslg-tree change can
move the version a fresh local checkout pulls.
v1.608.0 (Nov 2022) is the v1.6xx.x predecessor; v1.619.1 (Mar 2026)
is the latest non-preview tag in microsoft/DirectX-Headers. The
v1.7xx.x line is marked 'preview' upstream and isn't picked here.
cgmanifest.json: add the DirectX-Headers component (it was the only
fifth vendor missing from the manifest). Recorded at v1.619.1's
commit 9e393d6d so the next compliance scan picks up the right
upstream pin. Pre-existing trailing comma + relaxed-JSON formatting
preserved to keep this diff minimal -- not touching the manifest's
parser-quirks story in this PR.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Updates the recommended dev-clone tag in CONTRIBUTING.md to match the
new CI default ('24.0.1' in wslg-build's pipeline-shared.yml,
wslg-github-buddy.yml and wslg-github-release.yml). vendor/ itself is
.gitignored, so this is the only path by which a wslg-tree change can
move the version a fresh local checkout pulls.
23.1.0 is the May 2023 mesa release that has been pinned since
v1.0.17 of WSLg. 24.0.1 (Feb 2024) is what Azure Linux 3.0 base
ships and is the next-newer mesa tarball verifiably present on
azurelinuxsrcstorage.blob.core.windows.net (anything newer 404s),
so it's the obvious next step that keeps WSLg's mesa aligned with
the host distro and avoids ad-hoc mirroring.
WSLg only builds the swrast and d3d12 gallium drivers with LLVM
and Vulkan disabled (Dockerfile:240-245), so the upgrade just pulls
in fixes to that narrow surface; everything else mesa 24.0 added is
unbuilt.
cgmanifest.json: bump the mesa CommitHash to the upstream gitlab
commit for mesa-24.0.1 (3e361635) so compliance scanning sees the
same version CI actually consumes.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
Updates the pinned vendor component versions used by WSLg’s system-distro build to newer DirectX-Headers and Mesa revisions, aligning documentation and component governance metadata with the refreshed sources.
Changes:
- Bump the contributor clone instructions to DirectX-Headers
v1.619.1and Mesamesa-24.0.1. - Update
cgmanifest.jsonto point Mesa at themesa-24.0.1commit and add a new DirectX-Headers component entry.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| CONTRIBUTING.md | Updates local build instructions to clone newer DirectX-Headers and Mesa tags. |
| cgmanifest.json | Refreshes Mesa commit hash and adds DirectX-Headers registration for Component Governance. |
Comments suppressed due to low confidence (1)
cgmanifest.json:53
cgmanifest.jsonis invalid JSON due to the trailing comma after the final registration object (the comma after the last}before the closing]). This will break parsing for Component Governance tooling; remove the trailing comma so theRegistrationsarray ends with the last object followed directly by].
}
},
"DevelopmentDependency": false
},
]
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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
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.
Phase 1 of the vendor-source refresh: low-risk version bumps for the two components pinned by version-string in CI (DirectX-Headers and mesa). Companion change to wslg-build (the Azure DevOps pipeline) updates the same version defaults so CI consumes the new tarballs.
Changes
v1.608.0→v1.619.1(Nov 2022 → Mar 2026)mesa-23.1.0→mesa-24.0.1(matches what Azure Linux 3.0 ships, permicrosoft/azurelinuxSPECS/mesa/mesa.specon the3.0branch)CommitHashupdated to the 24.0.1 tag commit3e361635...9e393d6d..., v1.619.1) — this component previously had no cgmanifest entryWhy
azurelinuxsrcstorageblob CI downloads from (probed 24.0.2 through 25.2.x — all 404), so 24.0.1 is the realistic upper bound without re-plumbing CI's tarball source. Mesa's WSLg build flags (-Dgallium-drivers=swrast,d3d12 -Dvulkan-drivers= -Dllvm=disabled) are unchanged and continue to apply.Validation
./build-and-export.shcompletes all 88 Docker build steps with the new sources./etc/versions.txtcorrectly carries the new commit SHAs.swrastandd3d12gallium DRI drivers as before.Pairs with
Companion wslg-build PR
user/benhillis/phase1-vendor-bumpsupdates the correspondingmesaVersion/directxHeadersVersiondefaults indevops/pipeline-shared.yml,wslg-github-buddy.yml, andwslg-github-release.yml(plus the official-release enforcement check atpipeline-shared.yml:146-147).Not in scope
microsoft/*-mirrorworkingbranch tips at CI build time, not by this repo. See the upgrade plan / CVE summary for the follow-on phases.