fix: fix changelog formatting #1618
Merged
Conversation
This file contains 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
brendan-defi
approved these changes
Nov 13, 2024
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
alessey
approved these changes
Nov 14, 2024
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.
What changed? Why?
In the release process, our changelog is malformatted. This PR updates our
.changeset/config.jsonto use the proper formatter. This will make it easier to read changelogs on our Releases page and anywhere else they appear, plus it will make the release process easier.Before:
After this PR, each change will be formatted on separate lines.
Notes to reviewers
How has it been tested?
.mdfile resembling one that happens during our releasesbun: release version, output is as expected.