ci: fix semantic-release note generation (conventionalcommits v8)#7
Merged
Conversation
The v7 preset is incompatible with the conventional-changelog-writer bundled in semantic-release 24 and throws "Method Date.prototype.toString called on incompatible receiver [object Date]" during generateNotes, failing the version job before any tag is created. Bump to v8. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
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 first
Releaserun after #6 merged failed ingenerateNotes:semantic-release 24 (installed by
cycjimmy/semantic-release-action@v4) bundles aconventional-changelog-writerthat is incompatible with theconventional-changelog-conventionalcommits@7preset I pinned. Bump the pin to@8.The failure was clean — it errors before any tag is created, so no broken tag/release exists. The version analysis itself worked: it correctly read the
v1.11.0seed baseline, found thefix:commits from #5, and determined a patch (v1.11.1). Once this merges, the workflow re-runs and cuts v1.11.1 (full build path, since.github/changed alongsidecustom_components/).🤖 Generated with Claude Code