Skip to content

chore: upgrade @automerge/automerge to 3.2.6 across npm workspace#272

Merged
shikokuchuo merged 2 commits into
mainfrom
chore/upgrade-automerge-3.2.6
Jun 10, 2026
Merged

chore: upgrade @automerge/automerge to 3.2.6 across npm workspace#272
shikokuchuo merged 2 commits into
mainfrom
chore/upgrade-automerge-3.2.6

Conversation

@shikokuchuo

@shikokuchuo shikokuchuo commented Jun 10, 2026

Copy link
Copy Markdown
Member

Upgrades @automerge/automerge from 2.2.9 to 3.2.6 (pins in quarto-sync-client and preview-runtime, plus an explicit dependency in hub-client, which previously imported it undeclared).

  • Automerge 2.x expands documents into an uncompressed in-memory representation at load time, which could OOM the WASM instance during loadIncremental — surfacing as an intermittent "Unreachable code should not be executed" trap when opening a project.
  • Automerge 3 keeps the compressed representation at runtime (upstream reports >10x memory reduction) and is format-compatible

Automerge-repo 2.5.6 already accepts it (2.2.8 - 3). All ts-package and hub-client builds and test suites pass.

Automerge 2.x's uncompressed in-memory representation could OOM the WASM
instance during loadIncremental (intermittent 'Unreachable code should not
be executed' on project open, requiring a page refresh); automerge 3 keeps
the compressed representation at runtime. Also declares hub-client's
previously-undeclared direct dependency on @automerge/automerge.
@shikokuchuo shikokuchuo merged commit 35b9007 into main Jun 10, 2026
4 of 5 checks passed
@shikokuchuo shikokuchuo deleted the chore/upgrade-automerge-3.2.6 branch June 10, 2026 21:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant