Skip to content

docs(releasing): document constraint-floor bump + packages.lock refresh#31

Merged
nxships merged 1 commit into
mainfrom
docs/releasing-floor-bumps-lockfile
May 25, 2026
Merged

docs(releasing): document constraint-floor bump + packages.lock refresh#31
nxships merged 1 commit into
mainfrom
docs/releasing-floor-bumps-lockfile

Conversation

@nxships
Copy link
Copy Markdown
Collaborator

@nxships nxships commented May 25, 2026

Lessons from v0.1.2-test.1. PackageReference with [0.1.0,) resolves to the lowest satisfying version — new upstream releases need an explicit floor bump in the consumer csproj plus a packages.lock.json refresh, otherwise the build keeps using the old NuGet. Applies equally to stable and testing tags.

Hard-won lesson from v0.1.2-test.1: NuGet's PackageReference resolves
to the LOWEST version satisfying the range, not the latest. With a
constraint like [0.1.0,), a freshly-published NexusKit.Modules 0.1.1
keeps building against 0.1.0 unless the floor is moved forward.

Updates step 1 of "Cutting a release" to spell out:
- bump the floor in PlayerNexusTracker.Plugin.csproj (e.g. [0.1.0,) → [0.1.1,))
- refresh packages.lock.json (the sibling-clone swap means it looks
  empty locally for NexusKit refs, which is fine — CI re-evaluates)

Same discipline applies to pre-release / testing builds — without the
floor bump the testing zip ships with the same NuGets as the previous
stable, defeating the point.
@nxships nxships enabled auto-merge (squash) May 25, 2026 03:19
@nxships nxships merged commit b43f306 into main May 25, 2026
3 checks passed
@nxships nxships deleted the docs/releasing-floor-bumps-lockfile branch May 25, 2026 03:20
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