Skip to content

Gate MSVC releases on extracted-package execution with a controlled Windows environment #624

Description

@LunaStev

Part of #611. Difficulty: medium. Audit baseline: master 3950416e (2026-09-12).

Current evidence

.github/workflows/release.yml runs package smoke on the same runner that installed MinGW/LLVM. The ARM64 smoke clears WAVE_WINDOWS_ARM64_LINKER but still inherits provisioning paths. These tests cannot establish independence from build-machine tools and libraries.

Scope

Validate the actual x64 and ARM64 release archives in fresh jobs or equivalently controlled environments, isolated from checkout build outputs, compiler caches and MinGW paths. Test against the installation prerequisites chosen by the packaging task. If SDK installation is required, prove that the documented minimum setup is sufficient; do not claim a stock-Windows result from a Developer Prompt.

Completion criteria

After extraction, run wavec -V, verify host/default target, compile and execute ordinary hosted std workloads, and exercise required bundled tools from paths containing spaces/non-ASCII characters. Audit PE imports and assert no MinGW payload/runtime dependency. Log actual tool paths, architecture and installed prerequisites. A missing required component or failing program blocks release and retains useful artifacts.

Dependencies and boundaries

#621, #622, #625, #623; full ABI suites remain in their own issues.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    buildIssues related to building the project or compiling errors.ciGitHub CI or CIhelp wantedThe issue requires extra attention or help from others.needs testingIssues that require additional testing or verification.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions