Skip to content

Update .NET 12 SDK to 12.0.100-alpha.1.26562.108 - #12464

Merged
Amaury Levé (Evangelink) merged 2 commits into
mainfrom
dev/amauryleve/bump-net12-version
Nov 13, 2026
Merged

Amaury Levé (Evangelink) merged 2 commits into
mainfrom
dev/amauryleve/bump-net12-version

Conversation

@Evangelink

Copy link
Copy Markdown
Member

Pull request

Summary

Refreshes the repository's .NET 12 SDK pin to the newest public .NET 12 daily build, 12.0.100-alpha.1.26562.108 (runtime 12.0.0-alpha.1.26562.108, commit 8b22ce04ad5fa175ef5cd8f96c38fcba40e173dc), following the same pattern as the previous refresh (#12270).

  • global.json: both tools.dotnet and sdk.version pins.
  • eng/bazel/engineering-sdk.bzl: opt-in Bazel engineering SDK version, runtime, and all six host archive SHA-512 values (win/linux/osx x x64/arm64), checked against https://ci.dot.net/public-checksums/Sdk/12.0.100-alpha.1.26562.108/.
  • eng/bazel/verify-engineering-sdk.ps1 and eng/bazel/test-engineering-sdk-verifier.ps1: expected SDK commit, compiler identity (5.14.0-1.26562.108 (8b22ce04...)), and runtime version.
  • docs/bazel.md: current pin.
  • docs/decisions/bazel-build.md and docs/affected-test-selection.md: refresh evidence records.

Unchanged: Arcade SDK, the global.json runtimes (10.0.15, 11.0.0), the default published SDK 11 used by Bazel CI, the SDK 10.0.401 bootstrap, the independently pinned net8/9/10/11 reference packs, and the affected-tests minimum SDK gate (the new SDK satisfies it). Historical SDK versions in decision records are evidence and were intentionally not rewritten.

Design and decision record

Routine dependency refresh; no new design. The evidence is recorded in docs/decisions/bazel-build.md - SDK pin refresh (2026-11-13), and a short note was added to docs/affected-test-selection.md.

The latest build was selected via the public https://aka.ms/dotnet/12.0.1xx/daily/productCommit-<rid>.txt links, which point every host to the same 26562.108 build.

Demonstration

N/A. This is an SDK pin refresh with no user-visible output change. Validation evidence is below.

Validation and regression proof

All runs used source state ee4ff6852b552eae1b6923756eecaf9c4b9aec75 (or its identical uncommitted equivalent) on Windows x64 with the SDK restored into .dotnet/.

Command Result
.\eng\build.ps1 -restore -build Exit 0. Build succeeded, 0 errors, 8 warnings, all of them pre-existing NU1902/NU1903 NuGet audit advisories for System.Security.Cryptography.Pkcs 9.0.6 in MSTest.Analyzers.UnitTests. No new analyzer diagnostics.
pwsh -NoProfile -File .\eng\bazel\test-engineering-sdk-verifier.ps1 -EngineeringSdkDirectory .dotnet -PublishedSdkDirectory "C:\Program Files\dotnet" Exit 0. 12/12 verifier fixtures passed.
.\eng\bazel.ps1 build //:platform --extra_toolchains=@dotnet_engineering_toolchains//:all Exit 0. 79 native actions (task-owned output/cache roots).
.\eng\bazel.ps1 test //:protocol_contract_tests //:simple1_test --extra_toolchains=@dotnet_engineering_toolchains//:all --nocache_test_results Exit 0. //:protocol_contract_tests 28 cases passed and //:simple1_test 1 case passed, with fresh TRX results on the .NET 12 host.
.\eng\bazel.ps1 aquery 'deps(set(//:platform //:protocol_contract_tests //:simple1_test))' --extra_toolchains=... --include_param_files --output=jsonproto then verify-engineering-sdk.ps1 -ActionGraph ... -ExecutionRoot ... -TargetFrameworks net10.0 Exit 0. All 215 declared source actions use the new engineering SDK; the 2 bootstrap actions keep SDK 10.0.401; the net10.0 reference pack stays 10.0.14. (-TargetFrameworks net10.0 is required because these targets compile only that framework.)
pwsh -NoProfile -File .\eng\validate-affected-tests.ps1 -SelfTest -EnableAffectedTests true -EnableNonWindowsAffectedTests false and the same with false / true Both passed.

SDK identity was checked directly: csc -version reports 5.14.0-1.26562.108 (8b22ce04ad5fa175ef5cd8f96c38fcba40e173dc), the compiler runtimeconfig requests runtime 12.0.0-alpha.1.26562.108, the bundled max/default target framework is net12.0, and the default language versions are C# 15.0 and F# 11.2.

Not run or not covered:

  • CI has not run yet.
  • Native Bazel execution on non-Windows hosts was not repeated; those archives were checked only against the published checksums.
  • The affected-test collection and selection paths were not exercised end to end beyond the validator self-tests.
  • Local-only host note: this machine's very long PATH breaks build.cmd/dotnet-install, so PATH was deduplicated in-process before running the commands above. That is a host issue, not related to this change.

Test-value evidence

The executable contract affected here is the engineering SDK verifier, which pins the exact compiler identity it accepts.

  • Counterfactual (without the change): the previous verifier, eng/bazel/verify-engineering-sdk.ps1 blob 1d6497f20cd2d11ac088a4b516c1bd54a1ec6548, was run from an isolated copy with the new global.json against the valid four-framework VerifiedEngineeringCompiler fixture and the real new compiler. It exited 1 with Unexpected compiler identity: 5.14.0-1.26562.108 (8b22ce04...) after the compiler itself exited 0.
  • With the change: the updated verifier, given the identical input, exited 0 with "Engineering compiler verified for 4 declared source actions; requested reference packs preserved: net8.0, net9.0, net10.0, net11.0."

So the metadata update is required, and the verifier still rejects a mismatched SDK. The remaining changes are pin values validated by the build and the native Bazel runs above.

Refresh both global.json pins to the latest public .NET 12 daily SDK and
synchronize the opt-in Bazel engineering SDK registration (version, runtime,
six archive SHA-512s) and the verifier's compiler/runtime metadata.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot AI balanced review requested due to automatic review settings November 13, 2026 15:52
@github-actions github-actions Bot added the state/needs-review Awaiting review from the team. label Nov 13, 2026

@github-actions github-actions Bot left a comment

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.

🧪 Test quality review — PR #12464

Compared merge base e92578e3a4c076150c8b4174fbe04bd5b9df91d6 with head ee4ff6852b552eae1b6923756eecaf9c4b9aec75. Evidence applies to this head, not every intermediate commit.

Test-value evidence

Contract Scenario / expected outcome Test / assertion Counterfactual Status
Engineering SDK verifier pins the expected compiler identity (5.14.0-1.26562.108) A valid compiler fixture from the new SDK must be accepted; a mismatched identity must be rejected eng/bazel/test-engineering-sdk-verifier.ps1 fixtures (existing, expected values updated in this PR) Old verifier with the new SDK would reject the new compiler identity Static prediction. The PR description reports an executed before/after run, but no accessible record matches this head's variants.
SDK pins, archive SHA-512 values, docs Pin values must match the published SDK build None (data values) Not applicable Not applicable (validated by build and Bazel runs per the author, not verified here)

No test methods or parallelization configuration changed. Nothing was executed in this workflow.

🧵 Parallel safety

NOT_APPLICABLE. No changed tests or parallelization configuration were in scope.

Per-test assessment

Not applicable. No test methods were changed (the verifier script is PowerShell, not a graded C# test method).

No inline findings. Archive checksum values were not independently verified against the published checksums.

<sub>This advisory review is heuristic and non-blocking.

Re-run the combined review with /review-tests, or only the parallel-safety specialist with /parallel-audit.</sub>

🤖 Automated content by GitHub Copilot. Generated by the Test Quality Review on PR (on open / sync) workflow. · copilot · auto · ~27 AIC · ⌖ ~1 AIC · ⊞ 8.1K

@microsoft-github-policy-service microsoft-github-policy-service Bot added state/needs-review Awaiting review from the team. and removed state/needs-review Awaiting review from the team. labels Nov 13, 2026
@github-actions github-actions Bot added state/needs-review Awaiting review from the team. and removed state/needs-review Awaiting review from the team. labels Nov 13, 2026

@github-actions github-actions Bot left a comment

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.

Note

🤖 Automated review by GitHub Copilot. Generated by the Expert Code Review workflow. To request a follow-up action, reply by tagging @copilot directly.

Summary: no blocking findings.

Checked:

  • global.json (both pins), engineering-sdk.bzl (_SDK_VERSION/_RUNTIME_VERSION), verify-engineering-sdk.ps1 (commit 8b22ce04..., compiler 5.14.0-1.26562.108, runtime) and the verifier self-test fixtures all use 26562.108. I found no stale 26556.115 in any .bzl, .ps1, .json, .yml, .props or .bazel file.
  • The six SHA-512 values are well-formed 128-hex strings and all changed. I could not independently fetch the ci.dot.net manifests, so correctness of the hashes rests on the PR's stated verification.
  • docs/bazel.md now cites the exact global.json SDK. It was already stale (26509.101), so this is a good fix.

Non-blocking notes:

  • Older sections (docs/affected-test-selection.md lines ~98, 236, 319, and several docs/decisions/*.md files) still say 26556.115. They read as dated validation records, so leaving them is reasonable. The phrase "repository-pinned SDK" in affected-test-selection.md ~236 and ~319 is now slightly ambiguous, though.
  • The PR says CI was not run and affected-test paths were not re-exercised end to end. Please rely on CI for that.

Test-value evidence: behavior-preserving version bump. The PR reports 12 verifier fixtures passing, plus the old-versus-new verifier comparison. I did not execute these (read-only review of untrusted PR code).

@microsoft-github-policy-service microsoft-github-policy-service Bot added state/needs-review Awaiting review from the team. and removed state/needs-review Awaiting review from the team. labels Nov 13, 2026
@github-actions github-actions Bot added state/needs-review Awaiting review from the team. and removed state/needs-review Awaiting review from the team. labels Nov 13, 2026

Copilot AI left a comment

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.

🟢 Approval recommended

No active review issues were identified for the repository SDK and opt-in Bazel toolchain refresh.

No open issues 🎉

What changed in this PR

Refreshes TestFx’s repository SDK and opt-in Bazel engineering toolchain to .NET SDK 12.0.100-alpha.1.26562.108, continuing the previous SDK refresh without changing product APIs or default Bazel tooling.

Changes:

  • Updates both repository SDK pins and Bazel’s engineering SDK/runtime pins and six archive checksums.
  • Synchronizes compiler-verifier expectations and fixtures.
  • Updates documentation with the current pin and validation evidence.

Test-value evidence: The PR reports that, at revision ee4ff6852b552eae1b6923756eecaf9c4b9aec75, the previous verifier rejects the new compiler while the updated verifier accepts identical input; all 12 fixtures pass. These results were not independently executed here. CI, non-Windows native execution, and affected-test end-to-end validation remain unverified.

File Description
global.json Updates both repository SDK pins.
eng/​bazel/​verify-engineering-sdk.ps1 Updates expected compiler commit, identity, and runtime.
eng/​bazel/​test-engineering-sdk-verifier.ps1 Aligns verifier fixtures with the new SDK.
eng/​bazel/​engineering-sdk.bzl Updates engineering SDK/runtime versions and six archive checksums.
docs/​decisions/​bazel-build.md Records refresh rationale, validation, and limitations.
docs/​bazel.md Corrects the documented engineering SDK pin.
docs/​affected-test-selection.md Records validator results and end-to-end validation limits.

Review effort: Balanced

@microsoft-github-policy-service microsoft-github-policy-service Bot added state/needs-review Awaiting review from the team. and removed state/needs-review Awaiting review from the team. labels Nov 13, 2026
@github-actions github-actions Bot added state/approved Proposal approved; ready for implementation. and removed state/needs-review Awaiting review from the team. labels Nov 13, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Preliminary test-triage analysis — Azure Pipelines build 1679959

Preliminary: the build is still running, so other legs may change this conclusion.

Affected leg: microsoft.testfx (Build Linux Release), the Linux Release job, Test step. It runs MSTest.Acceptance.IntegrationTests on net12.0 x64.

Failures (FrameworkTargetingTests.NativeAotCompilerPack_MatchesBootstrappedRuntime, FrameworkTargetingTests.cs:54):

  • Case ("net10.0",10): the expected version is 10.0.15 but the actual is 10.0.14.
  • Case ("net11.0",11): the expected version is 11.0.0 but the actual is 11.0.0-rc.3.26522.148. The comparison is an exact string match, so the prerelease suffix fails it.

Assessment (confidence: medium):

  • Both failures are deterministic assertion mismatches with a stable signature, not a flake or an infrastructure problem. There is no retry or crash evidence.
  • They look related to this PR's .NET 12 SDK bump. The test compares the NativeAOT compiler pack version with the version of the bootstrapped runtime, and this PR changes the SDK and runtime used for that comparison. I have not confirmed the root cause from source.
  • The NU1902/NU1903 warnings for System.Security.Cryptography.Pkcs 9.0.6 are existing warnings and are not related to the test failures.

Next step: check how NativeAotCompilerPack_MatchesBootstrappedRuntime derives its expected version, and whether the 10.0.15 and 11.0.0 expectations are stale after the SDK update. The test may need to tolerate prerelease suffixes or pack/runtime patch skew. Compare with the Windows legs when they finish.

🤖 Automated content by GitHub Copilot. Generated by the Pipeline Test Triage workflow. · copilot · auto · ~38 AIC · ⌖ ~1 AIC · ⊞ 10.1K

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot AI balanced review requested due to automatic review settings November 13, 2026 17:44
@github-actions github-actions Bot added state/approved Proposal approved; ready for implementation. and removed state/approved Proposal approved; ready for implementation. labels Nov 13, 2026

@github-actions github-actions Bot left a comment

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.

🧪 Test quality review — PR #12464

Compared merge base 2cf92e4e5a532c91adb1035b52969fa8ad944a50 with head 6610464d2cb7c9879954afbcc5342b53ce95927a. Evidence applies to this head, not every intermediate commit.

Test-value evidence

Contract Scenario / counterfactual Result
Engineering SDK pin bump (global.json, eng/bazel/engineering-sdk.bzl, verifier scripts, docs) The SDK/runtime version, archive checksums and compiler commit move together from 26556.115 to 26562.108. A mismatch would be caught by verify-engineering-sdk.ps1, which checks the compiler version and commit, and by the verifier fixtures in test-engineering-sdk-verifier.ps1. Not applicable for new regression tests (data/config bump). Static prediction only: the verifier would detect a version/commit mismatch. Nothing was executed.

Gap: I did not check that the new checksums or the commit 8b22ce04... match the published SDK. That needs a CI run of the Bazel verifier.

🧵 Parallel safety

PARALLEL-SAFETY RESULT
STATUS: NOT_APPLICABLE
ASSEMBLIES:
none
COUNTS: A=0; B=0; C=0; D=0; Critical=0; High=0; Warning=0; Info=0
TOP_ACTIONS:
none
FINDINGS:
none
NOTES: No changed tests or parallelization configuration were in scope.
END PARALLEL-SAFETY RESULT

Per-test assessment

No test methods changed, so there is nothing to grade (Not applicable).

<sub>This advisory review is heuristic and non-blocking.

Re-run the combined review with /review-tests, or only the parallel-safety specialist with /parallel-audit.</sub>

🤖 Automated content by GitHub Copilot. Generated by the Test Quality Review on PR (on open / sync) workflow. · copilot · auto · ~26 AIC · ⌖ ~1 AIC · ⊞ 8.1K

@microsoft-github-policy-service microsoft-github-policy-service Bot added the state/needs-review Awaiting review from the team. label Nov 13, 2026
@github-actions github-actions Bot removed the state/needs-review Awaiting review from the team. label Nov 13, 2026
@github-actions github-actions Bot added state/approved Proposal approved; ready for implementation. and removed state/approved Proposal approved; ready for implementation. labels Nov 13, 2026

Copilot AI left a comment

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.

🟢 Approval recommended

No active review issues remain for the repository and opt-in Bazel SDK refresh.

No open issues 🎉

Review effort: Balanced

@Evangelink
Amaury Levé (Evangelink) merged commit 548d3bf into main Nov 13, 2026
31 checks passed
@Evangelink
Amaury Levé (Evangelink) deleted the dev/amauryleve/bump-net12-version branch November 13, 2026 19:47
@github-actions github-actions Bot removed the state/approved Proposal approved; ready for implementation. label Nov 13, 2026
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.

3 participants