Repository navigation
chore(ci) restore generated release notes and add regression coverage - #6414
Merged
Merged
Conversation
✅ Deploy Preview for fundamental-styles ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
droshev
force-pushed
the
chore/fix-release-notes
branch
from
October 5, 2026 15:14
183c9e9 to
c6dd8f3
Compare
InnaAtanasova
approved these changes
Oct 5, 2026
This branch was successfully deployed
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
2 participants
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.
Related Issue
Closes #6413
Description
Restores GitHub release-note generation broken during the
conventional-changelogv7 migration.The previous release tag was incorrectly passed through
.context(), which configures writer metadata but not the Git commit range. This caused the generator to inspect commits after the current tag and produce an empty body.This PR:
.commits({ from })to select the correct commit range