Skip to content

Respect npm prerelease range boundaries - #44

Merged
VikramLex merged 1 commit into
Graphicle-AI:mainfrom
dajiaohuang:w5/node-prerelease-range-boundary-20261114
Nov 21, 2026
Merged

VikramLex merged 1 commit into
Graphicle-AI:mainfrom
dajiaohuang:w5/node-prerelease-range-boundary-20261114

Conversation

@dajiaohuang

Copy link
Copy Markdown
Contributor

Summary

  • Apply npm's default prerelease filter to each Node version comparator set: a prerelease exporter is eligible only when a comparator names the same major, minor, and patch tuple.
  • Keep explicit prerelease opt-in working, and report excluded prereleases as version mismatches rather than linking them.

Evidence

With importer dependency ^1.2.0 and exporter version 1.3.0-beta.1, the previous matcher accepted the exporter even though npm's default range rules exclude prereleases on a different comparator tuple. The regression test covers that unresolved case and confirms ^1.3.0-beta.0 still accepts 1.3.0-beta.1.

Validation

  • cargo test --locked -p graphicle-memory --lib graph::cross_repo_imports::tests: 21 passed.
  • cargo fmt --check --manifest-path crates/graphicle-memory/Cargo.toml: passed.
  • git diff --check: passed.
  • cargo deny check: advisories, bans, licenses, and sources passed; existing duplicate-dependency warnings remain.

Signed-off-by: dajiaohuang <mikewushuwen@outlook.com>
@VikramLex
VikramLex merged commit 8aad76c into Graphicle-AI:main Nov 21, 2026
8 of 11 checks passed
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