Skip to content

Propose Lot 21: windows-rs 0.100, once windows itself ships - #27

Merged
geeooff merged 1 commit into
mainfrom
lot-21-windows-rs
Oct 17, 2026
Merged

geeooff merged 1 commit into
mainfrom
lot-21-windows-rs

Conversation

@geeooff

@geeooff geeooff commented Oct 17, 2026

Copy link
Copy Markdown
Owner

Lot 21 moves the windows-rs family to 0.100 once windows itself is published at that version. That will be a large migration: bindings are generated from the SDK headers, features are renamed, and signatures become raw.

Until then, windows-registry stays at 0.6. A trial on 0.100 built without code changes, but it doubled three core crates and needed Rust 1.95, with nothing gained. The maintainer decided to wait.

Other changes:

  • upgrade-dependencies skill: windows-rs crates move together, and a dependency that needs a newer Rust raises rust-version instead of being held back.
  • Lot 20 status: Dependabot's first automatic merge has been seen.

Design record and skill only; build.ps1 test passes.

🤖 Generated with Claude Code

windows-rs moved its smaller crates to 0.100 and held back windows while testing bindings now generated from the SDK headers. windows-registry 0.100 alone built unchanged but doubled three core crates and needed Rust 1.95, for nothing the program uses; decided with the maintainer to wait and move the family together in a lot of its own. The upgrade-dependencies skill now says so, and that a dependency needing a newer Rust raises rust-version rather than being held back. Lot 20's status says what was seen.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@geeooff
geeooff merged commit dd68162 into main Oct 17, 2026
2 checks passed
@geeooff
geeooff deleted the lot-21-windows-rs branch October 17, 2026 18:25
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.

1 participant