Skip to content

Bump Proc to 0.14.0, retry dotnet tool restore once on failure - #31

Merged
Mpdreamz merged 2 commits into
masterfrom
fix/proc-version-and-release-notes-cli
Sep 3, 2026
Merged

Mpdreamz merged 2 commits into
masterfrom
fix/proc-version-and-release-notes-cli

Conversation

@Mpdreamz

@Mpdreamz Mpdreamz commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Bumps the Proc build-script dependency from 0.9.1 to 0.14.0 (latest), matching the semantics (no shell expansion, throws on failure) already assumed elsewhere.
  • dotnet tool restore now retries once on failure: dotnet/sdk#53783 causes cold-cache restores of 2+ RID-specific tool packages (nupkg-validator and assembly-differ, both native-AOT now) to misattribute one package's DotnetToolSettings.xml to another. A retry always succeeds since the cache is warm afterward.

Test plan

  • dotnet build build/scripts/scripts.fsproj -c Release succeeds.

Made with Cursor

Mpdreamz and others added 2 commits September 2, 2026 21:40
Proc was pinned at 0.9.1; catches it up to 0.14.0 to match the semantics
(no shell expansion, throws on failure) the exec helper already assumes.

Also retries `dotnet tool restore` once on failure: dotnet/sdk#53783 causes
cold-cache restores of 2+ RID-specific tool packages (nupkg-validator and
assembly-differ, both native-AOT now) to misattribute one package's
DotnetToolSettings.xml to another. A retry always succeeds since the
resolver cache is warm afterward.

Co-authored-by: Cursor <cursoragent@cursor.com>
The plain "release-notes" package id is a DotnetToolSettings.xml v2 shim
that maps RIDs to per-RID sub-packages (see generatePackages) - it ships no
managed assembly of its own. Diffing against it found 0 assemblies and
failed the PR's own "Inspect public API changes" CI step:
https://github.com/nullean/release-notes/actions/runs/33674817669/job/100397363448

The portable, signed managed build lives in "release-notes.any" instead;
point previous-nuget at that. Verified locally against the real 0.11.0
package.

Co-authored-by: Cursor <cursoragent@cursor.com>
@Mpdreamz

Mpdreamz commented Sep 3, 2026

Copy link
Copy Markdown
Contributor Author

Also fixed generateApiChanges: it was diffing against the plain release-notes package id, which is just a DotnetToolSettings.xml v2 shim with no managed assembly (see this PR's own failing run). Now points at release-notes.any, which has the real signed build. Same latent bug existed in assembly-differ, nupkg-validator, and assembly-rewriter's own scripts; fixed there too.

@Mpdreamz
Mpdreamz merged commit d33e637 into master Sep 3, 2026
2 checks passed
@Mpdreamz
Mpdreamz deleted the fix/proc-version-and-release-notes-cli branch September 3, 2026 09:10
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.

1 participant