Skip to content

Keep Cratis NuGet families on one version in the package updater - #260

Merged
woksin merged 3 commits into
mainfrom
l189/259-nuget-family-lockstep
Nov 21, 2026
Merged

woksin merged 3 commits into
mainfrom
l189/259-nuget-family-lockstep

Conversation

@woksin

@woksin woksin commented Nov 21, 2026

Copy link
Copy Markdown
Contributor

Fixed

  • The shared NuGet package updater now moves every package in a Cratis family to the same version, so a scheduled update no longer leaves packages such as Cratis.Arc and Cratis.Arc.MongoDB on different versions. A family whose version is pinned only under a condition, or that has no stable version available for every member, is left unchanged with a warning, and repositories the updater skipped before are still skipped. (update-packages: keep Cratis NuGet package families on one version #259)

Resolve the highest common stable version for every locally pinned member of a Cratis family before the SDK runs, never lower a pin, defer whole families visibly, and keep Cratis packages out of the generic update.
Split parsing, planning and commands into small single-purpose functions with unchanged behavior and output.
…-framework callers

Pins reached through conditional imports, conditional items or Update overrides are left unchanged with a warning. Resolver edits are undone on every non-success exit, and a caller that only became filtered because of Cratis pins still skips on per-framework overrides.
@woksin woksin added the patch label Nov 21, 2026
@woksin woksin self-assigned this Nov 21, 2026
@woksin
woksin merged commit 5823f48 into main Nov 21, 2026
12 checks passed
@woksin
woksin deleted the l189/259-nuget-family-lockstep branch November 21, 2026 19:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant