Skip to content

Upgrade D3D12 Agility SDK to 1.619.1#2224

Merged
jevansaks merged 4 commits intomicrosoft:mainfrom
Traverse-Research:agility-1.619
Apr 3, 2026
Merged

Upgrade D3D12 Agility SDK to 1.619.1#2224
jevansaks merged 4 commits intomicrosoft:mainfrom
Traverse-Research:agility-1.619

Conversation

@MarijnS95
Copy link
Copy Markdown
Contributor

@MarijnS95
Copy link
Copy Markdown
Contributor Author

MarijnS95 commented Feb 26, 2026

For those interested, as usual I've also regenerated the bindings for the 719 preview here:

https://github.com/Traverse-Research/win32metadata/compare/agility-1.719
https://github.com/Traverse-Research/windows-rs/compare/windows-66-agility-sdk-1.719

@MarijnS95 MarijnS95 changed the title Upgrade D3D12 Agility SDK to 1.619.0 Upgrade D3D12 Agility SDK to 1.619. Mar 6, 2026
@MarijnS95 MarijnS95 changed the title Upgrade D3D12 Agility SDK to 1.619. Upgrade D3D12 Agility SDK to 1.619.1 Mar 6, 2026
@MarijnS95
Copy link
Copy Markdown
Contributor Author

@riverar reverse-ping, I'd love to just get #2170 and this in. Continuously rebasing it only to fix conflicts in the change file and undoing approvals that way isn't super productive.

@jevansaks
Copy link
Copy Markdown
Member

I believe I resolved the issue with the pipeline (needed to save the new packages to the feed). Do we need to get #2170 in first?

@jevansaks
Copy link
Copy Markdown
Member

@MarijnS95 I'm going to merge this change in. If you still want the other PR merged. This PR looks comprehensive so just close the other one if it's not needed anymore.

@jevansaks jevansaks merged commit 278d01c into microsoft:main Apr 3, 2026
8 of 9 checks passed
@MarijnS95 MarijnS95 deleted the agility-1.619 branch April 3, 2026 09:40
@MarijnS95
Copy link
Copy Markdown
Contributor Author

Thanks @jevansaks. This PR is purely based on top of #2170 so nothing is lost in the end. We just don't have a separate commit in history upgrading from 1.618.2 to 1.618.5 ahead of 1.619.1, but that is unlikely to be useful to anyone.

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.

2 participants