[release/11.0.1xx-preview6] Bump dotnet/dotnet to preview.6.26325.125 (BAR 320350) and remove sdk#54779 workaround - #36184
Merged
PureWeen merged 2 commits intoJun 29, 2026
Conversation
…workaround Updates all dotnet/dotnet (VMR) dependencies from 11.0.0-preview.6.26323.106 to 11.0.0-preview.6.26326.122 (BAR build 320483, VMR release/11.0.1xx-preview6 commit 1bff05b). This build is the first successful preview6 unified build that carries the aspnetcore fix dotnet/aspnetcore#67401 (commit 6bd759ad), the real upstream fix for the StaticWebAssets "Sequence contains more than one element" regression (dotnet/sdk#54779). Because the SDK now contains the fix, the temporary JSModulesEnabled=false workaround in the gallery sample is no longer needed and is removed, restoring the Blazor JS module manifest generation. global.json tools.dotnet is bumped to match the new SDK package version to avoid an SDK-band skew (NETSDK1147) on the macOS Build/Pack legs. Fixes #35953 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
|
🚀 Dogfood this PR with:
curl -fsSL https://raw.githubusercontent.com/dotnet/maui/main/eng/scripts/get-maui-pr.sh | bash -s -- 36184Or
iex "& { $(irm https://raw.githubusercontent.com/dotnet/maui/main/eng/scripts/get-maui-pr.ps1) } 36184" |
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the repo to consume a newer dotnet/dotnet VMR preview.6 build and removes the previously-added gallery sample workaround for dotnet/sdk#54779 (StaticWebAssets “Sequence contains more than one element”), relying on the upstream fix now present in the SDK.
Changes:
- Bump
dotnet/dotnet-sourced dependency versions/SHAs to11.0.0-preview.6.26326.122across dependency tracking files. - Align
global.jsontoolset (dotnet + Arcade/Helix MSBuild SDKs) to the same band. - Remove
JSModulesEnabled=falsefromMaui.Controls.Sample.csprojto restore JS module manifest generation.
Show a summary per file
| File | Description |
|---|---|
| src/Controls/samples/Controls.Sample/Maui.Controls.Sample.csproj | Removes the temporary JSModulesEnabled=false workaround now that the SDK fix is expected to be present. |
| global.json | Updates pinned dotnet SDK + Arcade/Helix MSBuild SDK versions to the new preview.6 band. |
| eng/Versions.props | Updates multiple dependency version properties to 26326.122. |
| eng/Version.Details.xml | Updates dependency versions and SHAs to match the new VMR commit (1bff05b...). |
Copilot's findings
- Files reviewed: 4/4 changed files
- Comments generated: 1
| @@ -146,13 +146,13 @@ | |||
| <TizenUIExtensionsVersion>0.9.0</TizenUIExtensionsVersion> | |||
github-actions
Bot
added
the
area-infrastructure
Member
Author
|
/azp run maui-pr-uitests |
|
No pipelines are associated with this pull request. |
Member
Author
|
/azp list |
|
CI/CD Pipelines for this repository: |
Member
Author
|
/azp run maui-pr-uitests, maui-pr-devicetests |
|
Azure Pipelines successfully started running 2 pipeline(s). |
PureWeen
added a commit
that referenced
this pull request
Jun 27, 2026
The prior commit (8c21599) bumped the VMR/SDK to preview.7.26326.125 (BAR 320499), which moved the SDK feature band to 11.0.100-preview.7. net11.0's android/macios workload manifests are only published on the preview.6 band, so provisioning requested Microsoft.NET.Sdk.{Android,iOS,MacCatalyst,tvOS,macOS}.Manifest-11.0.100-preview.7 packages that do not exist -> NU1101, failing every macOS/Windows leg at 'Provision SDK & Build BuildTasks'. This pins the VMR bits to preview.6.26326.122 (BAR 320483, SHA 1bff05b), the same build consumed by the preview6 PR #36184. It keeps net11.0 on its existing preview.6 band (manifest IDs unchanged from base) while still carrying the aspnetcore StaticWebAssets fix (sdk#54779). net11.0's own macios pin (26.5.11711-net11-p6) is preserved. eng/common reconciled to arcade beta.26326.122. The gallery JSModulesEnabled workaround removal is retained. Verified locally: Workloads.csproj restores cleanly under the preview.6 band (the exact NU1101 failure point). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This was referenced Jun 27, 2026
Open
releases.dot.net designates BAR 320350 (11.0.100-preview.6.26325.125, VMR commit a512c3ad) as the .NET 11 Preview 6 release build. This PR previously pinned BAR 320483 (preview.6.26326.122) — one build newer on the same channel, not the released escrow. Both builds pin the identical aspnetcore commit 6bd759ad (the #67401 backport of the StaticWebAssets / blazor.modules.json publish-crash fix, sdk#54779 / aspnetcore#67375), so the SWA fix is present either way. Re-pinning to 320350 makes MAUI coherent with the exact SDK that ships as Preview 6. Produced via: darc update-dependencies --id 320350 --source-repo dotnet/dotnet (global.json tools.dotnet synced manually; darc does not manage it). This branch's dotnet/macios pin (26.5.11714-net11-p6) preserved. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
PureWeen
changed the title
kubaflo
approved these changes
Jun 28, 2026
kubaflo
left a comment
kubaflo
left a comment
Contributor
There was a problem hiding this comment.
🤖 AI-generated review (orchestrator-verified). Mechanical VMR dependency bump — reviewed for version consistency + CI safety + workaround-removal validation.
✅ LGTM (content) — red maui-pr is environmental, not bump-caused
Identical change to its net11.0 twin #36186 (same SDK 26325.125, same JSModulesEnabled=false workaround removal for dotnet/sdk#54779), targeting release/11.0.1xx-preview6.
Version bump verified: preview.6.26323.106 → preview.6.26325.125 (+ matching beta.*) consistent across Version.Details.xml, Versions.props, global.json. Build + Pack (Windows/macOS, Debug/Release) all green; Blazor integration tests pass (macOS + Windows), validating the #54779 workaround removal.
CI classification — failures are NOT caused by this PR
maui-pr is red on three legs, but the content-identical twin #36186 (net11.0) is fully GREEN — including the same legs — with the same SDK. So the SDK bump itself doesn't break them:
| Failing leg (preview6) | Same leg on net11.0 twin | Classification |
|---|---|---|
Install dotnet preview without workloads |
✅ pass | transient feed/install |
Run Helix Tests (no issue records) |
✅ pass | infra/transient |
Run Integration Tests AOT windows (1 test) |
✅ pass (identical SDK) | branch-environmental flake |
Per the established policy (approve over a red rollup when the failures are confirmed not-PR-caused and the PR's own Build/Pack legs pass), this is good to merge. Recommendation: before merging, give the single AOT windows test a re-run to confirm it's the known flake (it passes on the identical-SDK net11.0 run, so I'm confident it is).
This was referenced Jun 29, 2026
PureWeen
added a commit
that referenced
this pull request
Jun 29, 2026
…) and remove sdk#54779 workaround (#36186) > [!NOTE] > Are you waiting for the changes in this PR to be merged? > It would be very helpful if you could [test the resulting artifacts](https://github.com/dotnet/maui/wiki/Testing-PR-Builds) from this PR and let us know in a comment if this change resolves your issue. Thank you! ### What Standalone bump of net11.0 to **dotnet/dotnet (VMR) build BAR 320350** — `11.0.100-preview.6.26325.125` (commit `a512c3ad`) — and **removal of the temporary `dotnet/sdk#54779` workaround** in the gallery sample. **BAR 320350 is the official .NET 11 Preview 6 release build** per releases.dot.net (ships 2026-07-14), so this pins MAUI to the exact SDK that ships. ### Why Build 320350 carries the aspnetcore fix (dotnet/aspnetcore#67375, backported via #67401) for the StaticWebAssets *"Sequence contains more than one element"* publish crash (dotnet/sdk#54779). With the fix in the SDK bits, the `JSModulesEnabled=false` workaround in `Maui.Controls.Sample.csproj` is no longer needed. This PR validates the workaround removal end-to-end on **net11.0**, where the `maui-pr-uitests` / `maui-pr-devicetests` pipelines run. ### Details - All 35 `dotnet/dotnet` deps → `11.0.0-preview.6.26325.125` (SHA `a512c3ad`), via `darc update-dependencies --id 320350 --source-repo dotnet/dotnet`. Stays on net11.0's existing **preview.6** SDK feature band. - `global.json` `tools.dotnet` → `11.0.100-preview.6.26325.125`; Arcade/Helix → `11.0.0-beta.26325.125`. - net11.0's own `dotnet/macios` pin (`26.5.11711-net11-p6`) is preserved. - Gallery sample workaround block removed. ### Build-selection history (for reviewers) 1. Initially pinned BAR 320499 (`preview.7.26326.125`) — this moved the SDK feature band to `11.0.100-preview.7`, but net11.0's android/macios workload manifests are only published on the **preview.6** band → provisioning requested nonexistent `Microsoft.NET.Sdk.*.Manifest-11.0.100-preview.7` packages → `NU1101`. 2. Corrected to BAR 320483 (`preview.6.26326.122`) — back on the preview.6 band. 3. Final: aligned to BAR **320350** (`preview.6.26325.125`) — the build releases.dot.net designates as the Preview 6 release. Both 320483 and 320350 pin the identical aspnetcore commit `6bd759ad` (the SWA fix), so 320350 carries the fix while being coherent with the shipping SDK. ### Relationship to other PRs - Companion to **#36184** (the equivalent change on `release/11.0.1xx-preview6`, also pinned to BAR 320350). - Intentionally separate from the maestro dependency-flow PR #36121 (older build without the fix). Fixes #35953 --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Note
Are you waiting for the changes in this PR to be merged?
It would be very helpful if you could test the resulting artifacts from this PR and let us know in a comment if this change resolves your issue. Thank you!
What
Bump
release/11.0.1xx-preview6to dotnet/dotnet (VMR) build BAR 320350 —11.0.100-preview.6.26325.125(commita512c3ad) — and remove the temporarydotnet/sdk#54779workaround in the gallery sample.BAR 320350 is the official .NET 11 Preview 6 release build per releases.dot.net (ships 2026-07-14), so this pins the preview6 branch to the exact SDK that ships.
Why
Build 320350 carries the aspnetcore fix (dotnet/aspnetcore#67375, backported via #67401) for the StaticWebAssets "Sequence contains more than one element" publish crash (dotnet/sdk#54779). With the fix in the SDK bits, the
JSModulesEnabled=falseworkaround inMaui.Controls.Sample.csprojis no longer needed.Details
dotnet/dotnetdeps →11.0.0-preview.6.26325.125(SHAa512c3ad), viadarc update-dependencies --id 320350 --source-repo dotnet/dotnet.global.jsontools.dotnet→11.0.100-preview.6.26325.125; Arcade/Helix →11.0.0-beta.26325.125.dotnet/maciospin (26.5.11714-net11-p6) is preserved.Relationship to other PRs
net11.0, also pinned to BAR 320350), where the UI/device-test pipelines run.Fixes #35953