Skip to content

(#22) Cake 2 catch-up - #23

Merged
gep13 merged 4 commits into
cake-contrib:developfrom
gep13:feature/issue-22-cake-2-catch-up
Aug 20, 2026
Merged

gep13 merged 4 commits into
cake-contrib:developfrom
gep13:feature/issue-22-cake-2-catch-up

Conversation

@gep13

@gep13 gep13 commented Aug 20, 2026

Copy link
Copy Markdown
Member

Per-Cake-major catch-up for Cake v2.0.0. Standard-shape arc — bumps Cake.Core / Cake.Testing from 1.0.0 to 2.0.0 and rotates addin TFMs.

Commit summary

  1. Cake.Core / Cake.Testing 1.0.0 → 2.0.0; addin TFM netstandard2.0 → net6.0 (Cake.Core 2.0.0 dropped netstandard2.0; matches sibling arcs Cake.Eazfuscator.Net v2.0.0 + Cake.ReSharperReports v2.0.0)
  2. demo/script cake.tool pin 1.3.0 → 2.3.0; strongnamesigner.cake #reference retargeted netstandard2.0 → net6.0
  3. demo/frosting Cake.Frosting pin 1.3.0 → 2.3.0; HintPath retargeted netstandard2.0 → net6.0
  4. CakeContribGuidelinesOmitTargetFramework for netcoreapp3.1 + net5.0 — both EOL; addin ships net6.0 only (matches sibling arcs)

Tests TFM stays net6.0; global.json SDK stays at 8.0.100.

Local verification

  • ./build.ps1 --target=Package — green (Test + DotNetCore-Pack; nupkg has lib/net6.0/ only)
  • ./demo/script/build.ps1 — green
  • ./demo/frosting/build.ps1 — green

Closes #22.

gep13 and others added 4 commits August 20, 2026 16:20
…TFM → net6.0

Cake.Core 2.0.0 dropped netstandard2.0 (ships net5.0/net6.0/netcoreapp3.1
only), so the addin retargets from netstandard2.0 to net6.0. Matches
sibling arcs Cake.Eazfuscator.Net v2.0.0 and Cake.ReSharperReports v2.0.0,
both of which shipped lib/net6.0/ only for their Cake 2 catch-ups.

Tests TFM stays net6.0 — the rotation floor for Cake 1-4 is unchanged.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…e → net6.0

Rotate cake.tool pin to the latest of the Cake 2 major (2.3.0). Retarget
the strongnamesigner.cake #reference path from netstandard2.0 to net6.0
in the same commit — the addin no longer publishes a netstandard2.0
folder to _PublishedLibraries, so demo/script would fail to load the
DLL if the two moved separately.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…tPath → net6.0

Rotate Cake.Frosting to latest-of-Cake-2 (2.3.0). Retarget the addin
HintPath from netstandard2.0 to net6.0 in the same commit — same
reasoning as demo/script's #reference: the addin no longer publishes
netstandard2.0 output.

TargetFramework for build/Build.csproj stays at net6.0 — Cake.Frosting
2.3.0 ships lib/{netcoreapp3.1,net5.0,net6.0} so net6.0 is fine.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…gets

Cake.Core 2.0.0 ships lib/{netcoreapp3.1,net5.0,net6.0}, and
CakeContrib.Guidelines' CCG0007 rule asks the addin to target all three
by default. Both netcoreapp3.1 (EOL Dec 2022) and net5.0 (EOL May 2022)
are past end-of-life and not installable via `actions/setup-dotnet` on
our `[ windows-2025, ubuntu-24.04 ]` matrix, so we omit them with
CakeContribGuidelinesOmitTargetFramework and ship net6.0 only —
matching sibling arcs Cake.ReSharperReports v2.0.0 and
Cake.Eazfuscator.Net v2.0.0.

CCG0009 ("recommended Cake 6.0.0") stays as a warning — expected until
the eventual v6.0.0 catch-up walks the addin all the way to Cake.Core 6.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

@gep13 gep13 left a comment

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

LGTM!

@gep13
gep13 merged commit cbe89fa into cake-contrib:develop Aug 20, 2026
2 checks passed
@gep13
gep13 deleted the feature/issue-22-cake-2-catch-up branch August 20, 2026 15:31
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.

Update Cake.StrongNameSigner add-in to target Cake v2.0.0

1 participant