[peinjoh]

No description provided.

[Copilot]

🟡 Changes recommended

Both new range types need TypeScript declarations that match their serialized WASM object representations.

2 open issues

• Prevent nullable TypeScript type for serialized version ranges · New
• Override Tsify type to match DynamicVersionRange serialization · New

What changed in this PR

Adds universal (all) and empty (none) VERS ranges, integrating them into the existing dynamic range API.

Changes:

• Introduces wildcard-only range types with constant membership results.
• Shares validation and serialization logic between both schemes.
• Extends dynamic parsing, serialization, TypeScript unions, and tests.

File	Description
src/​schemes/​none.rs	Implements the empty range and validation tests.
src/​schemes/​mod.rs	Exposes both new scheme modules.
src/​schemes/​all.rs	Implements the universal range and validation tests.
src/​range/​wildcard.rs	Shares wildcard validation, constraints, and serialization.
src/​range/​mod.rs	Registers the internal wildcard helper module.
src/​range/​dynamic.rs	Integrates both schemes into dynamic operations and tests.

_{Review effort: Balanced}

[Copilot]

🟢 Approval recommended

No active review issues are recorded for the addition of VERS all and none scheme support.

No open issues 🎉

2 resolved since last review

• Override Tsify type to match DynamicVersionRange serialization
• Prevent nullable TypeScript type for serialized version ranges

_{Review effort: Balanced}

[Copilot]

🟡 Changes recommended

Universal and empty ranges have incorrect membership semantics, generated TypeScript declarations reference undefined types, and parsing and deserialization accept constraints that produce invalid range strings.

4 open issues

• Use concrete version range types in TypeScript declarations · New
• Fix universal range membership for ordinary versions · New
• Make none range membership always return false · New
• Require wildcard-only constraints for all and none ranges · New

_{Review effort: Balanced}

[Copilot]

🟡 Changes recommended

Typed none ranges incorrectly match versions, and percent-encoded wildcards bypass validation, allowing ranges that fail JSON round-trip deserialization.

2 open issues

• Typed none ranges incorrectly match NoneVersion · New
• Percent-encoded wildcards bypass range validation · New

4 resolved since last review

• Make none range membership always return false
• Fix universal range membership for ordinary versions
• Use concrete version range types in TypeScript declarations
• Require wildcard-only constraints for all and none ranges

_{Review effort: Balanced}

[Copilot]

🔵 Needs a closer look

Human assessment is needed because tightened generic bounds break existing typed-range APIs, and wildcard validation remains inconsistent in the all and none schemes.

No open issues 🎉

2 resolved since last review

• Typed none ranges incorrectly match NoneVersion
• Percent-encoded wildcards bypass range validation

_{Review effort: Balanced}