fix(release): use compatible changelog preset - #77
Merged
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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.
Summary
conventional-changelog-conventionalcommits8.0.0, compatible with semantic-release 25 and changelog-writer 8.2Why
Release Prepare correctly selected v4.0.0 after PR #76, but preset 10 requires changelog-writer 9+ and failed during note generation. Preset 8 provides the current config API without exceeding the writer version bundled by semantic-release 25.
Verification
bun test tests/release-config.test.tsbun run checkbunx tsc -p packages/cli/tsconfig.json --noEmitgit diff --checkRelease decision
Yes. This release-pipeline correction should carry a patch signal. The unreleased breaking commit from PR #75 remains in the semantic-release range, so the next successful run should publish v4.0.0.
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.