chore(deps): raise every NexusKit floor to 0.5.1 - #36
Merged
Conversation
All five now name the release that is actually on the feed. Keeping the other four at 0.5.0 while Sync sat at 0.5.1 invited the mix that NU1603 reports and TreatWarningsAsErrors turns into a failed build — and it left the impression that the framework packages are versioned independently, which they are not: NexusKit publishes them together.
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
1 participant
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.
All five NexusKit floors now name the release that is on the feed.
NexusKit.Core[0.5.0,)[0.5.1,)NexusKit.GameData[0.5.0,)[0.5.1,)NexusKit.Persistence[0.5.0,)[0.5.1,)NexusKit.Ui[0.5.0,)[0.5.1,)NexusKit.Sync[0.5.1,)Leaving four at
0.5.0whileSyncsat at0.5.1was the mix that producedNU1603on the previous branch — a floor naming a version that never carried the library restores the substitute and warns, whichTreatWarningsAsErrorsturns into a failed build. It also implied the framework packages are versioned independently. They are not: NexusKit publishes them together, so their floors should move together.Ranges stay open-ended. A pinned floor would stop a consumer picking up a patch, and the workspace swaps these for project references anyway.