Conversation
The release of the whole backlog computed `2.0.0` and then failed. Both halves were config, not code. `noteKeywords` carried a bare `"BREAKING"` alongside the two keywords the Conventional Commits spec defines. The parser treats a note keyword at the start of a paragraph as a breaking-change declaration, so `22730338`'s body — which wraps onto a line beginning "breaking one assertion (exit=1), then restoring it (exit=0)." — declared one. Nine commits in this range contain the word "breaking" in ordinary prose; any of them could have done it, and none of them means it. The bare keyword buys nothing the spec keywords don't already cover and costs a major version to a line wrap, so it goes. `conventional-changelog-conventionalcommits` was floating on `^10`, whose preset requires `conventional-changelog-writer@9`; semantic-release 25 still bundles writer 8 through both `commit-analyzer` and `release-notes-generator`, so `generateNotes` died on a missing Handlebars helper after the version had already been decided. Pinned to `^9`, which is the major that matches the writer actually installed. `@commitlint/config- conventional` keeps its own nested 10 — it uses the parser, never the writer. Verified with `semantic-release --dry-run`: notes render, and the release type is minor.
|
🎉 This PR is included in version 1.24.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The merge of #67 landed on
main, but theReleaseworkflow failed before cutting a tag —mainis atb33c9decwith the last tag stillv1.23.0. Two config defects, no code involved.A wrapped prose line declared a breaking change.
.releaserc.jsonlisted a bare"BREAKING"innoteKeywordsnext to the two spec keywords. The conventional-commits parser reads a note keyword at the start of a paragraph as a breaking-change declaration, and22730338's body wraps onto a line beginningbreaking one assertion (exit=1)…. That is why the run announced2.0.0. Nine commits in the range use "breaking" as an ordinary word; none of them means it.The changelog preset outran its writer.
conventional-changelog-conventionalcommitsfloated on^10, whose preset needsconventional-changelog-writer@9. semantic-release 25 still bundles writer 8 in bothcommit-analyzerandrelease-notes-generator, sogenerateNotesdied on a missing Handlebars helper — after the version had been decided, which is why the log shows a version and then an error. Pinned to^9.Verified with
semantic-release --dry-run --no-ci: the notes render and the release type is minor. Merging this re-triggers the workflow onmain, which should cutv1.24.0.Merge commit, not squash.