Skip to content

ci: adopt EasyBuild.ShipIt for release automation#242

Merged
dbrattli merged 1 commit intomainfrom
ci/easybuild-shipit
Apr 16, 2026
Merged

ci: adopt EasyBuild.ShipIt for release automation#242
dbrattli merged 1 commit intomainfrom
ci/easybuild-shipit

Conversation

@dbrattli
Copy link
Copy Markdown
Collaborator

Summary

  • Add easybuild.shipit 2.0.0 to .config/dotnet-tools.json and a just shipit recipe
  • Switch .github/workflows/publish.yml to the two-job ShipIt pattern (opens a chore: release … PR on pushes to main, publishes to NuGet when that PR is merged)
  • Rework just pack / add just release so the version is read from CHANGELOG.md (matches Fable.Actor / Fable.Beam)
  • Add ShipIt frontmatter to CHANGELOG.md (last_commit_released pinned to the v5.0.0-rc.2 tag commit) so only new commits feed the changelog
  • Rewrite RELEASING.md to document the conventional-commit/ShipIt flow

Single root CHANGELOG.md — all packages release together.

Test plan

  • dotnet tool restore installs shipit
  • just shipit dry-run shows expected next version / changelog entry
  • Merge triggers the shipit-pr job; the release PR merge triggers the release job
  • NUGET_API_KEY secret is configured for the repo

🤖 Generated with Claude Code

Move release management to ShipIt with a single root CHANGELOG,
matching the setup used in Fable.Actor and Fable.Beam. ShipIt opens
a release PR on pushes to main and the publish workflow packs and
pushes to NuGet when that PR is merged.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@dbrattli dbrattli merged commit 5f72472 into main Apr 16, 2026
2 checks passed
@dbrattli dbrattli deleted the ci/easybuild-shipit branch April 16, 2026 00:19
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