Skip to content

chore(deps): bump NexusKit dependency floor to 0.2.1#23

Merged
nxships merged 2 commits into
mainfrom
chore/bump-nexuskit-to-0.2.1
May 25, 2026
Merged

chore(deps): bump NexusKit dependency floor to 0.2.1#23
nxships merged 2 commits into
mainfrom
chore/bump-nexuskit-to-0.2.1

Conversation

@nxships
Copy link
Copy Markdown
Contributor

@nxships nxships commented May 25, 2026

Summary

Raises the NexusKit framework floor across all six Modules csprojs from [0.1.0,) to [0.2.1,) so that:

  • the next Modules pack hard-depends on the freshly released NexusKit v0.2.1 (no accidental resolve to a stale 0.1.x or 0.2.0)
  • the resulting nupkg dependency metadata is honest about the actual minimum required framework version

packages.lock.json files are intentionally not regenerated in this PR — they'll be touched up the next time Dependabot or a developer runs dotnet restore --force-evaluate locally. The action ignores stale lockfiles for the purpose of release-note expansion.

Test plan

  • CI builds against NexusKit 0.2.1 (verified by floating-resolve at restore time on windows-2025-vs2026)
  • After merge: tag v0.1.2 to publish Modules v0.1.2 to GHP and verify the GitHub release body contains a 📦 Internal Dependency Changes block listing the NexusKit 0.1.0 → 0.2.1 jump

nxships added 2 commits May 25, 2026 14:56
NexusKit released v0.2.0 (and just now v0.2.1) with API changes; raise the minimum floor across all six Modules csprojs so consumers no longer accidentally resolve a stale 0.1.x.
Now that NexusKit v0.2.1 is published to GHP, pin the Modules floor there so the next pack pulls the actual latest framework instead of resolving any 0.2.x that happens to be cached.
@nxships nxships enabled auto-merge (squash) May 25, 2026 12:59
@nxships nxships merged commit c8cd8d1 into main May 25, 2026
2 checks passed
@nxships nxships deleted the chore/bump-nexuskit-to-0.2.1 branch May 25, 2026 13:01
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