Releases: getnyxdoc/nyxdoc
Release list
Nyxdoc v0.25.21
What changed
- Prevented read-only viewing, caret movement, editor initialization, and
normalization-only CRDT history from advancing or persisting a shared draft. - Kept draft timestamps, contributors, and actor attribution unchanged for
no-op updates, while preserving normal versioning for visible edits. - Clarified for MCP clients that
hasUncommittedChangesis the sole
authoritative pending-draft signal; draft version differences alone do not
mean that content needs to be saved.
Container image
ghcr.io/getnyxdoc/nyxdoc@sha256:480e00d09a8e701ba7d9e3eb66b6e98a0ad85616e976b719cd923918bd42c961
Full Changelog: v0.25.20...v0.25.21
Nyxdoc v0.25.20
What changed
- Fixed newly uploaded profile photos appearing broken after a successful save
by preserving a narrow read grant for the human who uploaded the image. - Kept unbound uploads hidden from every other user, so the profile-photo fix
does not broaden workspace media access or weaken document authorization.
Container image
ghcr.io/getnyxdoc/nyxdoc@sha256:0de06147e6b6007f1bfd92d8e026fd6225c3b222c58b3e48dcbc7f07851182be
Full Changelog: v0.25.19...v0.25.20
Nyxdoc v0.25.19
What changed
- Made the one-time
0.25.17update bridge preserve a logical installation
symlink so Docker Compose continues to address the already-running project. - Made update receipts and interrupted-update validation read backup manifest
evidence through the application container when the host lifecycle account
cannot traverse the container-owned backup bind mount. - Extended the standalone safe bridge through
0.25.18, whose checked-in
updater still reaches the host-only manifest reader before target code can
repair it. - Added lifecycle regressions for symlinked installations and host-unreadable
backup directories while retaining manifest hashing, source provenance, and
full backup verification.
Container image
ghcr.io/getnyxdoc/nyxdoc@sha256:42c1b4a7fed0a2d37998ab6e9e7193105f0195bb00f5a62d395b472dedc2c0c4
Full Changelog: v0.25.18...v0.25.19
Nyxdoc v0.25.18
What changed
- Made collaboration writes durable before broadcast, rechecked authorization
for every live mutation, and preserved shared drafts across Strict Mode,
reconnects, and document-tree moves. - Unified document moves behind the canonical collaboration command boundary,
including same-parent reorder idempotency and conflict-safe cross-parent
moves without implicitly committing a dirty body. - Closed media, OAuth consent, archive, trash, workspace, and agent lifecycle
authorization races with live mutation barriers and fail-closed scope checks. - Added verified media-history and backup-checkpoint migrations, stronger
offline migration rehearsals, and a one-time v0.25.17 update bridge that
drains accepted editor writes before the legacy updater creates its backup. - Expanded real Chrome and Edge collaboration coverage, release-candidate
browser verticals, migration/restore checks, and lifecycle interruption tests. - Reworked release publication around an immutable qualified image digest,
source provenance, serialized aliases, idempotent recovery, and readable
changelog-derived GitHub Release notes. - Kept block-insertion patches retry-safe across lost MCP responses by checking
idempotency before reapplying operations, while preserving the separate page
title and leading-heading validation rule on the first write. - Updated the supported runtime dependencies and removed known production npm
audit findings. - Made first-install and disaster-recovery paths portable across Docker hosts
by accepting image-seeded empty media directories and normalizing data,
media, and backup ownership before offline migrations. - Made linked text consistently show a hand cursor, including links whose
visible label is rendered by nested editor elements. - Made historical release qualification portable to non-root baseline images
by staging its temporary fixture driver under the container-writable/tmp
directory instead of the read-only application tree. - Made CI fetch release tags needed by lifecycle tests and exercise table-cell
focus through real browser input so collaboration stress coverage reflects
user behavior instead of synthetic DOM selection.
Container image
ghcr.io/getnyxdoc/nyxdoc@sha256:bc5dc60ad8e057694ede3fde7d10221b959afc3aae20cdc9cf253132c276475e
Full Changelog: v0.25.17...v0.25.18
Nyxdoc v0.25.17
What changed
- Allow documents with an uncommitted shared draft to move across parents
without implicitly saving or discarding the draft body. - Commit only the canonical parent metadata, rebase the shared draft onto that
structural revision, and preserve its dirty state until the user explicitly
saves the document. - Make cross-parent metadata, sibling ordering, draft rebasing, and retry
receipts one atomic operation with stale-state and rollback protection. - Exclude retained diagnostic source snapshots from production TypeScript and
ESLint project traversal so release checks validate the active source tree.
Container image
ghcr.io/getnyxdoc/nyxdoc@sha256:0ef97003f027d3a931ddc76f0d4a329357dc3b1b89fe3c382a8a07924d7d77fe
Full Changelog: v0.25.16...v0.25.17
Nyxdoc v0.25.16
What changed
- Use native mouse movement as the desktop document-tree drag path while
retaining pointer events for touch and pen input, covering embedded browser
controllers that do not emit a complete pointer-event sequence. - Keep the same movement threshold, before/inside/after placement rules,
navigation suppression, and automatic tree scrolling across both input
paths. - Exercise the desktop mouse path in Chrome and Edge browser regression tests.
Container image
ghcr.io/getnyxdoc/nyxdoc@sha256:537d0106b74dd8f7a8d8a9a2c32d7dcc050e5bc00cb0ad168ba70868c7afc8b2
Full Changelog: v0.25.15...v0.25.16
Nyxdoc v0.25.15
What changed
- Changed document-tree movement from browser-native HTML drag events to
pointer-based dragging so pressing and moving a row works consistently in
embedded browsers as well as Chrome and Edge. - Prevented a document title link from intercepting the drag as a browser link
drag, while preserving ordinary clicks for document navigation. - Kept before, inside, and after placement feedback, cross-parent moves, and
automatic destination expansion under the same pointer interaction.
Container image
ghcr.io/getnyxdoc/nyxdoc@sha256:0f28fe971a9064a330fb2f9f8893d9e200a823e3bbb02959bd508398b4cd48f6
Full Changelog: v0.25.14...v0.25.15
Nyxdoc v0.25.14
What changed
- Fixed stable updates from an older official digest-pinned deployment so the
updater advances the container image together with the source revision
instead of reporting success while continuing to run the previous image. - Reconcile an out-of-date official image even when the source checkout is
already on the target release, allowing an interrupted or partial update to
be repaired safely with the same one-line update command. - Keep release qualification pinned to its exact immutable candidate digest
while continuing to preserve explicitly configured third-party images.
Container image
ghcr.io/getnyxdoc/nyxdoc@sha256:d353892db6732a457970e4ec0d430eac36fca9ee27705472c3b6c0b91da87b07
Full Changelog: v0.25.13...v0.25.14
Nyxdoc v0.25.13
What changed
- Extended document-tree drag and drop from sibling-only reordering to
Confluence-style placement before, inside, or after another document while
preserving the moved document's complete child subtree. - Record cross-parent moves as canonical structural revisions through the
shared-draft pipeline, and refuse to move a document with an uncommitted
draft so content is never committed implicitly. - Added cycle prevention, explicit inside-drop feedback, automatic expansion
of the destination document, and browser regression coverage for moving a
top-level document under another document.
Container image
ghcr.io/getnyxdoc/nyxdoc@sha256:1f6b380564bf127e9e9c68a277cd10c2d24e322fcf68f56112f2adc7c02a25cd
Full Changelog: v0.25.12...v0.25.13
Nyxdoc v0.25.12
Qualified immutable container: ghcr.io/getnyxdoc/nyxdoc@sha256:7319988b2ede77fd6b10a0301c088af3d0daf032baeee487bac82c06a48ab0b7
Full Changelog: v0.25.11...v0.25.12