Repository navigation
fix(release): use a compatible Conventional Commits preset - #64
Merged
Merged
Conversation
Deploying atrinik-website with
|
| Latest commit: |
70afebe
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://7bdb0e6d.atrinik-website.pages.dev |
| Branch Preview URL: | https://fix-release-notes-compatibil.atrinik-website.pages.dev |
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.
Summary
Fix the Semantic Release failure on main after the dependency update: release-note generation fails with
Missing helperbecause the newer Conventional Commits preset requires a newer changelog writer than the stable release plugin supplies.Implementation / behavior
^9.3.1dependency range and standard npm lockfile.Validation
70afebeb4f9543e3b9b0af7a9e4f156a077d6543.Limitations / follow-up
Actual release publication runs after merge; local validation invokes only release-note generation and packaging dry runs. This PR does not approve a merge or dispatch a release/deployment.