Visitar URL original
chore(sdk): Align Uno.Sdk.Private with the 7.0 stables by agneszitte · Pull Request #26282 · unoplatform/uno · GitHub
Skip to content

chore(sdk): Align Uno.Sdk.Private with the 7.0 stables - #26282

Closed
agneszitte wants to merge 1 commit into
release/stable/7.0from
dev/agzi/sdk-private-70-stables
Closed

agneszitte wants to merge 1 commit into
release/stable/7.0from
dev/agzi/sdk-private-70-stables

Conversation

@agneszitte

Copy link
Copy Markdown
Member

GitHub Issue: relates to https://github.com/unoplatform/private/issues/1251 (Uno Platform 7.0 release)

PR Type:

🏗️ Build or CI related changes

What changed? 🚀

The Uno.Sdk.Private manifest (src/Uno.Sdk/packages.json) on the 7.0 line still pinned the 7.0 dev builds of the packages that now have 7.0 stables. This moves them to those stables, the same kind of change as #25899 for 6.7:

Group Before After
settings (Uno.Settings.DevServer) 2.0.0-dev.23 2.0.1
AppMcp (Uno.UI.App.Mcp) 2.0.0-dev.7 2.0.1
Resizetizer 2.0.0-dev.36 2.0.1
sdkextras 6.4.0-dev.15 6.4.1
UnoFonts 2.10.0-dev.9 2.10.1
CSharpMarkup 7.0.0-dev.33 7.0.1
Extensions 8.0.0-dev.150 8.0.1
Toolkit 11.0.0-dev.157 11.0.1
Themes 9.0.0-dev.61 9.0.1
Reactor 0.1.0-dev.77 0.1.1
WasmBootstrap net10.0 / net11.0 10.1.0-dev.284 / 11.1.0-dev.5 10.1.1 / 11.0.9

Unchanged on purpose:

  • hotdesign stays on its 2.0 dev build: Hot Design 2.0 builds on this manifest, so it's released after it.
  • The Uno.Maui previews (UnoMaui, UnoRetarget) and the .NET 11 RC pins (Maui, MicrosoftLoggingConsole for net11.0).

Why now: Hot Design requires its Licensing version to match the one Uno.Sdk.Private declares, so Hot Design 2.0 can't build on the stable Licensing 2.0.1 until this manifest declares it.

Checked before opening:

  • Every version exists: on the internal feed (the 7.0 stables aren't on nuget.org yet), Uno.Fonts 2.10.1 on nuget.org.
  • No pinned package is below the dependency floor of another pinned package.
  • The packages already built on 7.0.29 need Uno.WinUI 7.0.29 or later, with no exact pins and no dev dependencies, so they don't need a rebuild.
  • Uno.Sdk.AddInVersionValidation.Tests passes locally on this branch (.NET 11 RC3), with Licensing 2.0.1, App MCP 2.0.1 and Hot Design 2.0.0-dev.2, and also with Hot Design 2.0.0-dev.65.
  • The nuget.org existence check runs in warning-only mode on release branches. The template and add-in test jobs add the internal feed.

7.0 only: master is on the 7.1 dev line.

PR Checklist ✅

🤖 Generated with Claude Code

Moves the Uno.Sdk.Private manifest (src/Uno.Sdk/packages.json) on the 7.0 line
from the 7.0 dev builds to the 7.0 stables: Uno.Settings.DevServer 2.0.1,
Uno.UI.App.Mcp 2.0.1, Uno.Resizetizer 2.0.1, Uno.Sdk.Extras 6.4.1,
Uno.Fonts 2.10.1, C# Markup 7.0.1, Uno.Extensions 8.0.1, Uno.Toolkit 11.0.1,
Uno.Themes 9.0.1, Uno.Microsoft.UI.Reactor 0.1.1 and Uno.Wasm.Bootstrap
10.1.1 (net10.0) / 11.0.9 (net11.0).

Hot Design stays on its 2.0 dev build (2.0 is not released yet), and the
Uno.Maui previews and the .NET 11 RC pins are unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions github-actions Bot added the area/sdk Categorizes an issue or PR as relevant to the Uno.Sdk label Nov 10, 2026
@github-actions

github-actions Bot commented Nov 10, 2026 •

Copy link
Copy Markdown
Contributor

Claude finished @agneszitte's task in 17s —— View job


PR review: Align Uno.Sdk.Private with the 7.0 stables

  • Read the diff against origin/release/stable/7.0
  • Checked it against the PR description
  • Posted findings

Verdict: ship, once the one question below is answered.

Scope: src/Uno.Sdk/packages.json only, 12 version bumps. The diff matches the table in the PR description exactly, and the intentionally unchanged pins (hotdesign, UnoMaui, UnoRetarget, and the .NET 11 RC pins) are untouched.

Issues: 0 blocking, 1 question, 0 nits.

  • The question is on the WasmBootstrap net11.0 override. 11.0.9 is lower than the previous 11.1.0-dev.5, so it is a SemVer downgrade, unlike the other bumps. It is probably intentional, but please confirm.

Cross-cutting notes:

  • No code, tests, or XAML changed, so the runtime-test, sample, and style rules don't apply.
  • I couldn't check that the stables exist on the internal feed, because they aren't on nuget.org. I'm relying on the author's pre-check.
  • Conventional Commit title (chore(sdk): ...) is fine.
  • The PR is correctly scoped to 7.0.

Comment thread src/Uno.Sdk/packages.json
"net10.0": "10.1.0-dev.284",
"net11.0": "11.1.0-dev.5"
"net10.0": "10.1.1",
"net11.0": "11.0.9"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Question (non-blocking): 11.0.9 sorts below the previous 11.1.0-dev.5 in SemVer, so for net11.0 this is a downgrade, not a dev→stable promotion like the others. Presumably intentional (the 11.0.x line being the stable one for the 7.0 release), but please confirm it's not a typo for 11.1.x, and that nothing pinned (e.g. a template or add-in) requires Uno.Wasm.Bootstrap ≥ 11.1.0-dev.5 features. Worth a sentence in the PR description, since the table presents it as "after" like the rest.

@agneszitte

Copy link
Copy Markdown
Member Author

Closing for now to avoid a mistake: the 7.0 Uno.Sdk.Private manifest moves to the 7.0 stables after the 7.0 release, as it did for 6.5 and 6.7, and ships in the first 7.0 service release. For 7.0, Hot Design keeps Licensing 2.0.0-dev.23, the version Uno.Sdk.Private 7.0.29 declares.

@agneszitte agneszitte closed this Nov 10, 2026
@unodevops

Copy link
Copy Markdown
Contributor

🤖 Your WebAssembly Sample App stage site is ready! Visit it here:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/sdk Categorizes an issue or PR as relevant to the Uno.Sdk

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants