• v0.1.0 48e7f0e338

    Bump windows crate 0.61 -> 0.62 (fixes the Windows release build)
    Release / build (aarch64-apple-darwin) (push) Waiting to run
    Release / build (x86_64-apple-darwin) (push) Waiting to run
    Release / build (aarch64-unknown-linux-gnu) (push) Waiting to run
    Release / build (x86_64-pc-windows-msvc) (push) Waiting to run
    Release / publish GitHub Release (push) Blocked by required conditions
    Release / build (x86_64-unknown-linux-gnu) (push) Failing after 30s

    ZacharyZhang-NY released this 2026-07-18 09:52:48 +00:00 | 98 commits to main since this release

    The third Windows release failure was a genuine cross-version type
    mismatch: process-wrap 9.1.0 wraps windows 0.62's
    PROCESS_CREATION_FLAGS in its CreationFlags wrapper, while the
    workspace pinned windows 0.61 — the CREATE_NEW_PROCESS_GROUP |
    CREATE_NO_WINDOW constants we pass came from a different nominal type.
    Aligning the workspace on 0.62 leaves a single windows crate in the
    graph.

    Windows code cannot be compiled on this host (a full cross-typecheck
    dies in ring's C build), so the change is verified by auditing every
    windows-crate item our cfg(windows) code imports (25 items across 9
    files) plus all seven Win32_* feature names against the actual
    windows-0.62.2 registry sources — all present — and by confirming
    process-wrap's CreationFlags field is the same 0.62 type our call site
    now names.

    Downloads