Skip to content

ci: use conventionalcommits release preset - #222

Merged
brunobritodev merged 1 commit into
masterfrom
ci/release-config
Nov 18, 2026
Merged

brunobritodev merged 1 commit into
masterfrom
ci/release-config

Conversation

@brunobritodev

Copy link
Copy Markdown
Member

Why

#218 was squash-merged as feat!: target .NET 10 and update dependencies, and the squash dropped the commit body. The publish run on master found no release: "Analysis of 1 commits complete: no release".

semantic-release's default angular preset does not understand the ! breaking-change marker. It only sees the BREAKING CHANGE: footer, and the squash removed it. Version 8.0.0 was never published, and NuGet still shows 7.1.2.

What

  • .releaserc: commit-analyzer and release-notes-generator now use the conventionalcommits preset, which recognizes feat!: / fix!: in the header.
  • Publish workflow: adds conventional-changelog-conventionalcommits@8 to extra_plugins. This is the preset package for semantic-release 24.
  • actions/checkout@v7 and actions/setup-dotnet@v6. They were bumped on the feat!: target .NET 10 and update dependencies #218 branch after it had already been merged.

Expected result

After merge, semantic-release analyzes the commits since v7.1.2. That includes 7ed5417 feat!: ..., so it should publish 8.0.0 to nuget.org (net10.0 packages).

I could not dry-run semantic-release locally. Please check the "Semantic Release" step log after the merge: it should say "The next release version is 8.0.0".

@brunobritodev
brunobritodev merged commit 4b84519 into master Nov 18, 2026
1 check passed
@brunobritodev
brunobritodev deleted the ci/release-config branch November 18, 2026 00:00
@github-actions

Copy link
Copy Markdown

🎉 This PR is included in version 8.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant