Skip to content

(#24) Cake 3 catch-up - #25

Merged
gep13 merged 3 commits into
cake-contrib:developfrom
gep13:feature/issue-24-cake-3-catch-up
Aug 20, 2026
Merged

gep13 merged 3 commits into
cake-contrib:developfrom
gep13:feature/issue-24-cake-3-catch-up

Conversation

@gep13

@gep13 gep13 commented Aug 20, 2026

Copy link
Copy Markdown
Member

Per-Cake-major catch-up for Cake v3.0.0. Standard-shape arc.

Commit summary

  1. Cake.Core / Cake.Testing 2.0.0 → 3.0.0; addin TFMs net6.0 → net6.0;net7.0; drop the CakeContribGuidelinesOmitTargetFramework block that v2.0.0 added (Cake.Core 3 no longer ships the EOL TFMs it was suppressing)
  2. demo/script cake.tool pin 2.3.0 → 3.2.0
  3. demo/frosting Cake.Frosting pin 2.3.0 → 3.2.0

Tests TFM stays net6.0; global.json SDK stays at 8.0.100. demo/script #reference + demo/frosting HintPath stay on net6.0 (still in _PublishedLibraries alongside net7.0).

Local verification

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

Matches sibling arcs Cake.Eazfuscator.Net v3.0.0 + Cake.ReSharperReports v3.0.0 (both shipped lib/{net6.0,net7.0}/).

Closes #24.

gep13 and others added 3 commits August 20, 2026 16:48
…t7.0 TFM

Cake.Core 3.0.0 ships lib/{net6.0,net7.0} — dropping netcoreapp3.1 +
net5.0 (both EOL) and adding net7.0. The addin's TFMs move from
`net6.0` to `net6.0;net7.0` to match. Sibling arcs (Cake.Eazfuscator.Net
v3.0.0, Cake.ReSharperReports v3.0.0) both shipped the same pair.

Drop the CakeContribGuidelinesOmitTargetFramework block that v2.0.0
added — it existed to suppress CCG0007 for netcoreapp3.1 + net5.0 back
when Cake.Core 2 still demanded them. Cake.Core 3 no longer ships
those TFMs, so CCG no longer asks the addin to target them; the
suppression is vestigial.

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

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Rotate cake.tool pin to the latest of the Cake 3 major (3.2.0). No
#reference retarget needed — the addin still publishes net6.0 into
_PublishedLibraries (alongside net7.0), and the script's existing
net6.0 reference is still valid.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Rotate Cake.Frosting to latest-of-Cake-3 (3.2.0). No HintPath retarget
needed — the addin still publishes lib/net6.0/ (alongside net7.0), and
the demo's HintPath already targets net6.0.

TargetFramework for build/Build.csproj stays at net6.0 — Cake.Frosting
3.2.0 ships lib/{net6.0,net7.0} so net6.0 is fine.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@gep13
gep13 force-pushed the feature/issue-24-cake-3-catch-up branch from 4511fa0 to ebd6659 Compare August 20, 2026 15:48

@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 fab587f into cake-contrib:develop Aug 20, 2026
2 checks passed
@gep13
gep13 deleted the feature/issue-24-cake-3-catch-up branch August 20, 2026 15:56
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 v3.0.0

1 participant