Repository navigation
[Release] Version packages - #5174
Merged
Merged
Conversation
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
zbeyens
force-pushed
the
changeset-release/main
branch
7 times, most recently
from
October 17, 2026 00:01
0319f30 to
818f6f4
Compare
zbeyens
force-pushed
the
changeset-release/main
branch
5 times, most recently
from
October 17, 2026 18:53
2ce6f20 to
1b6bed4
Compare
zbeyens
force-pushed
the
changeset-release/main
branch
from
October 18, 2026 18:52
8a6a5fc to
a5b5140
Compare
Member
Author
|
Merging because PR #5190 checked auto release. |
This file contains hidden or 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
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.
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/ai@53.3.18
Patch Changes
@platejs/markdown.@platejs/core@53.3.18
Patch Changes
#5172 by @dylans – Upgrade to slate 0.142.1, slate-dom 0.142.0, slate-react 0.142.0 and slate-hyperscript 0.138.3.
#5190 by @dylans – Upgrade to slate 0.146.0, slate-dom 0.146.0 and slate-react 0.145.1.
@platejs/markdown@53.3.18
Patch Changes
#5185 by @ybai08 –
allowedNodes,disallowedNodesandallowNodeto the children of bold, italic and strikethrough, sodisallowedNodes: ['a']also removes a link inside**…**. AnallowedNodeslist now needstext, and any inline type such asa, listed to keep that content inside these marks, as it already does outside them.#5179 by @dylans –
htmlnodes and HTML comments deserialize as a text leaf withrawHtml: trueand serialize back unescaped. Before,<b>x</b>came back as\<b>x\</b>, and comments were dropped.<b>`code`</b>no longer loses its backticks, and a list or paragraph inside a block tag such as<details>keeps the blank lines around it, so it still renders as Markdown.#5177 by @dylans –
[text][id],[id][],[id],![alt][id]) asaandimgnodes using the matching definition's URL. They were dropped before, so a paragraph holding only a reference link came back empty.#5178 by @dylans –
now, so Markdown output no longer carries invisible characters at the start or end of a paragraph.platejs@53.3.18
Patch Changes
@platejs/core,@platejs/slate,@platejs/utils.@platejs/slate@53.3.18
Patch Changes
#5172 by @dylans – Bring the bundled history plugin up to date with slate-history:
withoutSaving,withoutMerging,withMergingandwithNewBatchrestore their flags when the callback throws, so one failed transform no longer stops history from recording.withNewBatchkeeps the enclosing batch's split.withoutMerging, a transform's normalization stays in the same undo step as the transform, so undoing it no longer leaves an unnormalized document behind.editor.hasRangeandeditor.api.hasRangenow share one implementation built on slate'shasRange, and still returnfalsefor a missing range.#5190 by @dylans – Bring the bundled history plugin up to date with slate-history 0.144.0:
editor.tf.setChildren(children), which applies an outside document through operations instead of replacingeditor.children, so the selection, refs and history stay valid. Each call is its own undo step, separate from typing before and after it.editor.tf.withoutSaving. Saved steps are moved past each unsaved operation, so a block inserted above earlier typing, or text inserted before it, no longer makes undo remove the wrong characters. Steps whose content was removed, or that can no longer be applied, are dropped.#5172 by @dylans – Upgrade to slate 0.142.1, slate-dom 0.142.0, slate-react 0.142.0 and slate-hyperscript 0.138.3.
#5190 by @dylans – Upgrade to slate 0.146.0, slate-dom 0.146.0 and slate-react 0.145.1.
cb4f514by @github-actions[bot] – Updatedslate,slate-dom,slate-react.@platejs/utils@53.3.18
Patch Changes
@platejs/core,@platejs/slate.@platejs/test-utils@53.3.18