Skip to content

docs(releasing): correct PackageReference resolution behaviour#20

Merged
nxships merged 1 commit into
mainfrom
docs/releasing-correct-package-resolution
May 25, 2026
Merged

docs(releasing): correct PackageReference resolution behaviour#20
nxships merged 1 commit into
mainfrom
docs/releasing-correct-package-resolution

Conversation

@nxships
Copy link
Copy Markdown
Contributor

@nxships nxships commented May 25, 2026

Same lesson from PlayerNexusTracker v0.1.2-test.1 propagated here. [X.Y.Z,) is a range that resolves to the lowest satisfying version, not a floating reference. Promotion to a new stable needs an explicit floor bump.

The opening paragraph claimed [0.1.0,) is "floating" and that
consumers pick up new versions automatically — both wrong. NuGet's
PackageReference resolves to the LOWEST satisfying version, so a new
release on the feed does nothing for consumers until they bump the
range floor and refresh packages.lock.json.

Also fixes the "Cross-repo testing cascade" promotion step which told
consumers to revert pinned pre-release versions back to [0.1.0,) —
that would re-resolve to 0.1.0, not 0.2.0. The correct move is to
raise the floor to [0.2.0,) instead.
@nxships nxships enabled auto-merge (squash) May 25, 2026 03:20
@nxships nxships merged commit 4b7efac into main May 25, 2026
2 checks passed
@nxships nxships deleted the docs/releasing-correct-package-resolution branch May 25, 2026 03:21
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