docs(releasing): document constraint-floor bump + packages.lock refresh#31
Merged
Merged
Conversation
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Lessons from v0.1.2-test.1.
PackageReferencewith[0.1.0,)resolves to the lowest satisfying version — new upstream releases need an explicit floor bump in the consumer csproj plus apackages.lock.jsonrefresh, otherwise the build keeps using the old NuGet. Applies equally to stable and testing tags.