This repository was archived by the owner on Oct 20, 2026. It is now read-only.
Repository navigation
docs: status read from the code at 0.1.0-canary.16 - #5
Merged
Merged
Conversation
The header now reads from main at @paged-media/data 0.1.0-canary.16 (published 2026-10-13), peers plugin-api / plugin-sdk >=0.2.45-canary.0, tests against canvas-wasm 0.71.1 and the 0.2.45-canary.0 contract. What changed in the document: - The universal-binding section was headed "On branch, not on main". It is on main and published since canary.11; the protocol-71 notes no longer refer to unreleased branches, and the typed commands are ten (media.paged.data.merge joined them). - Ten commands, seven menu entries, five panels: Data overview, the empty states and the module door (canary.15) are described. - Limits: the documents door is released (contract 0.2.41); the IDML import's paragraph mark between placeholders is fixed from protocol 70; editor ADR 218 is on the editor's main; canary.10 is the first package that ships DuckDB; the document label (setDocumentMetadata) is released in core v0.69.0. - Internal tracker ids dropped from the lines touched. - A Releases table: canary.10 to canary.16 and what each added. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… the placeholder fix Merge to a new document needs the host's documents door; the editor's main implements it (editor ADR 219). Core's plugin-publish pin (c140a98) contains the IDML import fix for the paragraph mark between adjacent placeholders, which is why the test asserts the fix from protocol 70. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Docs only:
docs/status.mdbrought up to date withmainand the published@paged-media/data0.1.0-canary.16. No code changes.What changed
mainat 0.1.0-canary.16 (published 2026-10-13), peers plugin-api / plugin-sdk>=0.2.45-canary.0, tests against canvas-wasm 0.71.1 and the 0.2.45-canary.0 contract.om/universal-binding, not onmain". The work is onmainand published since canary.11.Visible="false"are described as protocol-71 behaviour.media.paged.data.mergewas added in canary.16.main; the text said it was on a branch.setDocumentMetadatawas released in core v0.69.0; the host-gap table said "not yet released".Does merging publish?
No.
publish.ymlruns aftervitestsucceeds onmain.docs/is not an input ofscripts/package-hash.mjs(its inputs are the bundle and host-modelsrc/, the manifests, the build config,tsconfig.base.jsonandscripts/vendor-duckdb.sh), so the bump check passes. data-bundle's version 0.1.0-canary.16 is already on npm, so the publish step skips it. Nothing ships.🤖 Generated with Claude Code