The committed packages.lock.json files require Microsoft.NET.ILLink.Tasks 10.0.12, which is what SDK 10.0.401 resolves. The pin said 10.0.100,
so the existing dotnet restore MarkdownViewr.Windows.slnx -p:Platform=x64 --locked-mode step fails with NU1004 both under exactly 10.0.100 and
under a newer 10.0.4xx (the native Windows runner has 10.0.403). rollForward: latestFeature had been hiding this on GitHub's windows-latest
image. setup-dotnet will now install the SDK the locks were generated with.
Verified (real run, Windows host, central engine script dotnet-verify.ps1, exact SDK 10.0.401, no source change beyond this file)
locked restore, -warnaserror build, dotnet format --verify-no-changes (with the WinUI app project built first, as the existing format-projects input does for AppKit)
MarkdownViewr.Windows.Core.Tests: 677 passed of 677, 0 skipped
line coverage MarkdownViewr.Windows.Core: 100%
legacy Node job commands (scripts.yml): npm ci --ignore-scripts, npm run lint, npm test (8 of 8, 0 skipped), npm audit signatures all pass
Not covered by that run (unchanged, not hidden)
UI suites (reader-regressions, UiTests, need an interactive desktop), installed-updates, the powershell job in scripts.yml.
One-line change: `global.json` SDK `10.0.100` -> `10.0.401`.
## Why (existing build blocked)
The committed `packages.lock.json` files require `Microsoft.NET.ILLink.Tasks` 10.0.12, which is what SDK 10.0.401 resolves. The pin said 10.0.100,
so the existing `dotnet restore MarkdownViewr.Windows.slnx -p:Platform=x64 --locked-mode` step fails with NU1004 both under exactly 10.0.100 and
under a newer 10.0.4xx (the native Windows runner has 10.0.403). `rollForward: latestFeature` had been hiding this on GitHub's `windows-latest`
image. `setup-dotnet` will now install the SDK the locks were generated with.
## Verified (real run, Windows host, central engine script `dotnet-verify.ps1`, exact SDK 10.0.401, no source change beyond this file)
- locked restore, `-warnaserror` build, `dotnet format --verify-no-changes` (with the WinUI app project built first, as the existing
`format-projects` input does for AppKit)
- `MarkdownViewr.Windows.Core.Tests`: 677 passed of 677, 0 skipped
- line coverage `MarkdownViewr.Windows.Core`: 100%
- legacy Node job commands (`scripts.yml`): `npm ci --ignore-scripts`, `npm run lint`, `npm test` (8 of 8, 0 skipped), `npm audit signatures` all pass
## Not covered by that run (unchanged, not hidden)
UI suites (`reader-regressions`, `UiTests`, need an interactive desktop), `installed-updates`, the `powershell` job in `scripts.yml`.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
global.json pinned 10.0.100, but every packages.lock.json requires Microsoft.NET.ILLink.Tasks 10.0.12 (what SDK 10.0.401 resolves). Under exactly 10.0.100, or under a newer 10.0.4xx such as 10.0.403, locked restore fails NU1004 ('package reference ... has changed from [10.0.12, ) to ...'). rollForward latestFeature hid this on GitHub's windows-latest runner image. Pinning 10.0.401 makes the existing restore --locked-mode, build, format and test steps reproducible; no other file or setting changes.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
One-line change:
global.jsonSDK10.0.100->10.0.401.Why (existing build blocked)
The committed
packages.lock.jsonfiles requireMicrosoft.NET.ILLink.Tasks10.0.12, which is what SDK 10.0.401 resolves. The pin said 10.0.100,so the existing
dotnet restore MarkdownViewr.Windows.slnx -p:Platform=x64 --locked-modestep fails with NU1004 both under exactly 10.0.100 andunder a newer 10.0.4xx (the native Windows runner has 10.0.403).
rollForward: latestFeaturehad been hiding this on GitHub'swindows-latestimage.
setup-dotnetwill now install the SDK the locks were generated with.Verified (real run, Windows host, central engine script
dotnet-verify.ps1, exact SDK 10.0.401, no source change beyond this file)-warnaserrorbuild,dotnet format --verify-no-changes(with the WinUI app project built first, as the existingformat-projectsinput does for AppKit)MarkdownViewr.Windows.Core.Tests: 677 passed of 677, 0 skippedMarkdownViewr.Windows.Core: 100%scripts.yml):npm ci --ignore-scripts,npm run lint,npm test(8 of 8, 0 skipped),npm audit signaturesall passNot covered by that run (unchanged, not hidden)
UI suites (
reader-regressions,UiTests, need an interactive desktop),installed-updates, thepowershelljob inscripts.yml.Co-Authored-By: Claude Sonnet 5.5 noreply@anthropic.com
global.json pinned 10.0.100, but every packages.lock.json requires Microsoft.NET.ILLink.Tasks 10.0.12 (what SDK 10.0.401 resolves). Under exactly 10.0.100, or under a newer 10.0.4xx such as 10.0.403, locked restore fails NU1004 ('package reference ... has changed from [10.0.12, ) to ...'). rollForward latestFeature hid this on GitHub's windows-latest runner image. Pinning 10.0.401 makes the existing restore --locked-mode, build, format and test steps reproducible; no other file or setting changes. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>