Repair release PR generation

[SegaraRai]

Summary

• restore the published fraci package version to 0.18.0, matching npm and the latest changelog entry
• format packages/core/CHANGELOG.md with Vite+ after Changesets updates it
• validate that the package version matches the latest changelog version during the normal check task

Root cause

The monorepo migration reset packages/core/package.json to 0.17.0 even though fraci 0.18.0 was already published and documented. Changesets therefore generated a second 0.18.0 section and used the older section for the Version Packages PR body. In addition, the generated changelog was not passed through the repository formatter, causing the release PR CI to fail.

Impact

The next release PR update will target 0.19.0, include the current pending changesets in its description, and produce a changelog that passes Vite+ formatting checks.

Validation

• pnpm exec vp run check
• simulated pnpm exec vp run changeset:version, which generated fraci 0.19.0 with the expected release notes
• pnpm exec vp check against the generated release state

Summary by CodeRabbit

• Chores
  • Updated the core package to version 0.18.0.
  • Added release validation to ensure package versions match the latest changelog entry.
  • Integrated release checks into the standard validation workflow.
  • Added automatic changelog formatting during version updates.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 58b68e68-6be9-422e-981a-e2cd0758d582

📥 Commits

Reviewing files that changed from the base of the PR and between 977b2f0 and 7448275.

📒 Files selected for processing (3)

• packages/core/package.json
• packages/core/scripts/check-release-state.mjs
• vite.config.ts

---

📝 Walkthrough

Walkthrough

The core package version is now 0.18.0. A release-state script compares the package version with the latest changelog heading. The check task runs this validation, and the changeset version task formats the changelog.

Changes

Release state workflow

Layer / File(s)	Summary
Release version validation packages/core/package.json, packages/core/scripts/check-release-state.mjs, vite.config.ts	The package version is set to 0.18.0. The validation script checks the latest changelog heading and reports missing or mismatched versions. The check task runs the validation.
Changeset version formatting vite.config.ts	The changeset:version task runs Changesets versioning and formats packages/core/CHANGELOG.md.

Estimated code review effort: 2 (Simple) | ~10 minutes

Sequence Diagram(s)

sequenceDiagram
  participant CheckTask
  participant ReleaseValidation
  participant ReleaseFiles
  CheckTask->>ReleaseValidation: Run check:release-state
  ReleaseValidation->>ReleaseFiles: Read package.json and CHANGELOG.md
  ReleaseFiles-->>ReleaseValidation: Return package and changelog versions
  ReleaseValidation-->>CheckTask: Report validation result

Loading

Poem

A rabbit checks the version line,
Then trims the changelog neat and fine.
“0.18.0” hops in view,
The release state matches true.
The check task thumps its feet—
A tidy release is complete!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly describes the primary change: repairing release pull request generation and release-state handling.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/fix-release-pr-metadata

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}