0.12.6

Rich text: an indented code fence parses as code

A patch release. All six packages move to 0.12.6 together. Only @silverprotocol/richtext changes. The spec revision stays 1.0.0-draft.8.

@silverprotocol/richtext

  • A fenced code block indented one to three spaces, or continuing a list item, now parses as a code block. CommonMark allows up to three spaces before a fence, and a fence can continue a list item at the item’s content column. The parser matched only an unindented fence, so an indented one parsed as paragraphs. Up to the fence’s own indent is now stripped from each line of its body. List items still hold inline content only, so a fence that continues an item closes the list and follows it as a top-level code-fence block, and a later item opens a new list that keeps its number. The AST types don’t change.

The other five packages change only their version.

Who should upgrade

A host that renders model text with @silverprotocol/richtext, where a model may indent a code fence or put one inside a list.

Wire version

1.0.0-draft.8, unchanged. No normalizer and no part of @silverprotocol/core changes, so every package emits and folds exactly as 0.12.5 does.

npm’s provenance for all six 0.12.6 packages attests typescript-sdk commit e79566b4.