Repository navigation
Tooling and release-hygiene fix on top of v3.2. No bridge source changed — the d3d9.dll in this release is byte-identical to the one in v3.2.
Fixed: the audited-bridge importer had been refusing to run
tools/migration/import-audited-bridge.ps1 guards the overlay allowlist with a hardcoded entry count, and tests/bridge-importer-path-safety-test.ps1 carries the same number as a canary. When the ProperShaders guard and state-ring files were added to tools/migration/bridge-overlay-files.txt, the allowlist grew from 38 to 42 entries but both guards stayed at 38.
Consequences:
- The importer threw
Unexpected Bridge overlay count: 42and refused to import anything. - Windows CI failed at
Run testsonbridge-importer-path-safety. The build itself was clean.
Both guards now read 42. The 38 in tests/bridge-migration-manifest-test.ps1 is deliberately unchanged — that test validates the 67f1750 baseline git blob, not the working tree.
On version naming
VERSION names the SDK/ABI generation, not the release. It is a separate axis from the v3.x release tag line and stays at 0.1.0-alpha.1. Windows CI names every package from VERSION, so the packages below carry the SDK generation in their filenames — that is intentional, not a packaging mistake.
Assets
| File | What it is | sha256 |
|---|---|---|
SA-RenderStack-v0.1.0-alpha.1-sdk.zip |
SDK headers and import libraries | 4cf0ce06…17ef2d |
SA-RenderStack-v0.1.0-alpha.1-split.zip |
The audited Bridge overlay split | 78777584…632b9e8 |
SA-RenderStack-v0.1.0-alpha.1-symbols.zip |
Debug symbols | 6a2c7833…b368a839 |
SA-RenderStack-v0.1.0-alpha.1-source-manifest.json |
Per-file source manifest with hashes | 45d46fbd…4cdeb1 |
d3d9.dll |
The bridge proxy, identical to v3.2 | 0de68a85…8fd0d076 |
The four packages are produced by Windows CI from this tag. d3d9.dll is a local build (VS 18 Build Tools, MSVC 14.51.36231, toolset v145, C++23, Win32 Release); it loads the D3D9 backend from backend/dxvk-gta at runtime, which is not included.
Verification
Windows CI green on this tag: build, full test suite, package, package-layout verification.
In-game verification of the ProperShaders guard remains pending — see v3.2.