Skip to content

Conversation

@complexspaces
Copy link
Member

This PR supersedes #200 and adds semver compatibility for windows-sys 0.60.x.

The existing GitHub action that checks the multi-version compatibility should correctly work here. We already know 0.59 works (and that release series is now deprecated), so there's no need to introduce an additional step to perform 0.59 -> 0.60 checking independently.

I had to update errno to allow cargo update -p windows-sys to reach 0.60 instead of stopping at 0.59 still. I verified this correct update behavior locally as well:

 cargo update -p windows-sys
    Updating crates.io index
     Locking 12 packages to latest compatible versions
      Adding windows-link v0.1.3
      Adding windows-sys v0.59.0
      Adding windows-sys v0.60.2
      Adding windows-targets v0.53.3
      Adding windows_aarch64_gnullvm v0.53.0
      Adding windows_aarch64_msvc v0.53.0
      Adding windows_i686_gnu v0.53.0
      Adding windows_i686_gnullvm v0.53.0
      Adding windows_i686_msvc v0.53.0
      Adding windows_x86_64_gnu v0.53.0
      Adding windows_x86_64_gnullvm v0.53.0
      Adding windows_x86_64_msvc v0.53.0
 cargo clippy --all-features
    Blocking waiting for file lock on build directory
    Checking windows_x86_64_msvc v0.53.0
    Checking windows-targets v0.53.3
    Checking windows-sys v0.60.2
    Checking arboard v3.6.0 (github\arboard)
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 2.73s

@complexspaces
Copy link
Member Author

The GitHub Action verifying version compatibility correctly pulled in 0.60.x into the build, not 0.59:
image

@complexspaces complexspaces merged commit 26a96a6 into master Aug 21, 2025
11 checks passed
@complexspaces complexspaces deleted the windows-sys-updates-2025 branch August 21, 2025 20:32
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