[gwdp]

Why

I broke the changelog with a multiline changeset in #4683, and the release failed fmt:check.

How

Format the generated changelog before committing the release so multiline changesets pass fmt:check.

Like expo/expo, we configure Changesets to run Oxfmt during changeset version. That formats the package changelogs, but we write our custom root changelog afterward. Run Oxfmt on it too, adding the missing blank line before the next bullet while preserving multiline entries.

Authorship and LLM use

I wrote this description and reviewed the changes. Codex implemented and tested the change.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 75.75%. Comparing base (864b11e) to head (6c2342b).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #4773   +/-   ##
=======================================
  Coverage   75.75%   75.75%           
=======================================
  Files        1059     1059           
  Lines       52813    52813           
  Branches    11566    11566           
=======================================
  Hits        40001    40001           
  Misses      11832    11832           
  Partials      980      980           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[github-actions]

Subscribed to pull request

File Patterns	Mentions

Generated by CodeMention

Warning: The preamble and epilogue options in commentConfiguration are deprecated. Use template instead.

[devin-ai-integration]

Devin Review found 1 potential issue.

[gwdp]

Updating to allow multi-line instead and align with expo/expo

[github-actions]

❌ This PR needs a valid changeset. Run yarn changeset, select the changed packages and the bump type, and commit the new file in .changeset/. Do not edit CHANGELOG.md: the release generates it. The "Validate changesets" step log lists the problems.
⏩ If this PR doesn't require a changelog entry, such as if it's an internal change that doesn't affect the user experience, you can add the "no changelog" label to the PR. The label does not allow edits to CHANGELOG.md files.