[Release] Version packages#5055
Conversation
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6cf6a12a04
ℹ️ 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".
|
|
||
| ### Patch Changes | ||
|
|
||
| - [`279fdae`](https://github.com/udecode/plate/commit/279fdae77739b0c549dc2c6d9c65b4512c62d9ce) by [@github-actions[bot]](https://github.com/github-actions%5Bbot%5D) – Updated `slate-react`. |
There was a problem hiding this comment.
Move the slate-react note to @platejs/core
This release note is attached to @platejs/slate, but the dependency update it describes is in packages/core/package.json (slate-react), while @platejs/slate does not depend on slate-react at all. When publishing 53.3.3, @platejs/core gets the runtime dependency change with an empty changelog and @platejs/slate advertises a change it does not ship, so consumers looking at package-specific release notes are pointed at the wrong package.
Useful? React with 👍 / 👎.
| @@ -1,7 +1,7 @@ | |||
| [ | |||
| { | |||
| "changelogUrl": "https://github.com/udecode/plate/blob/d142cfb5b9358d97b3ec67448e7e00be41f067a4/packages/plate/CHANGELOG.md", | |||
| "content": "`@platejs/core`\n\n### Breaking Changes\n\n- Prepare v54 beta prerelease versioning. ([#5031](https://github.com/udecode/plate/pull/5031))\n\n`@platejs/slate`\n\n### Breaking Changes\n\n- Prepare v54 beta prerelease versioning for Slate. ([#5031](https://github.com/udecode/plate/pull/5031))\n\n[`v53.3.2...v54.0.0-beta.0`](https://github.com/udecode/plate/compare/v53.3.2...v54.0.0-beta.0) · By [@felixfeng33](https://github.com/felixfeng33)", | |||
| "content": "`@platejs/core`\n\n### Breaking Changes\n\n- Prepare v54 beta prerelease versioning. ([#5031](https://github.com/udecode/plate/pull/5031))\n\n`@platejs/slate`\n\n### Breaking Changes\n\n- Prepare v54 beta prerelease versioning for Slate. ([#5031](https://github.com/udecode/plate/pull/5031))\n\n[`v53.3.3...v54.0.0-beta.0`](https://github.com/udecode/plate/compare/platejs%4053.3.3...platejs%4054.0.0-beta.0) · By [@felixfeng33](https://github.com/felixfeng33)", | |||
There was a problem hiding this comment.
Keep beta release compares off later stable tags
When this stable 53.3.3 entry is inserted, the already-published v54.0.0-beta.0 note is rewritten to compare platejs@53.3.3...platejs@54.0.0-beta.0. That beta was dated 2026-06-16 while 53.3.3 is dated 2026-07-08, so the release page now links the beta notes to a backwards/cross-channel diff instead of the delta that produced the beta release.
Useful? React with 👍 / 👎.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
platejs@53.3.3
Patch Changes
@platejs/core,@platejs/slate,@platejs/utils.@platejs/slate@53.3.3
Patch Changes
279fdaeby @github-actions[bot] – Updatedslate-react.@platejs/utils@53.3.3
Patch Changes
@platejs/core,@platejs/slate.@platejs/core@53.3.3
@platejs/test-utils@53.3.3