fix: preserve release note formatting - #79
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
commit: |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6777cca234
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| { | ||
| "printWidth": 100, | ||
| "semi": false, | ||
| "singleQuote": true |
There was a problem hiding this comment.
Match Vite+'s trailing-comma default
When a changeset contains an embedded multiline function call or declaration, the locked Changesets formatter uses Prettier 2.8.8's trailingComma: "es5" default, while Vite+'s oxfmt uses "all". The version command can therefore still generate a CHANGELOG.md that pnpm exec vp check rejects, only for a different syntax than the example fixed here. Mirror trailingComma: "all" in this compatibility configuration, or derive both formatter configurations from one authoritative source.
AGENTS.md reference: AGENTS.md:L77-L77
Useful? React with 👍 / 👎.
Add a Prettier compatibility configuration and format the generated changelog so Changesets release PRs remain compatible with Vite+ formatting.