Repository navigation
zn v0.7.0: record assistant edits for review, no long dashes - #7
Merged
Merged
Conversation
Vault.WriteNote wrote the file and only then checked that it was in a note folder, so write_note on a path under .zennotes created that file before failing with "not in a known folder". The other edits already checked first (editNote). WriteNote now checks first too; notes, new or existing, are written as before.
ZenNotes 2.68.0 can show what an assistant changed in a note and let the user accept or reject each change. It needs the note's previous text, which only the MCP server sees: before write_note, append_to_note, prepend_to_note, insert_at_line, replace_in_note or toggle_task changes a note of a local vault, zn mcp now writes it to .zennotes/agent-edits/<note>.json, makes the edit, and stores the note as it now reads, naming the assistant from the client's initialize name. The record mirrors the desktop's @shared/agent-edits and its TypeScript MCP server, and the writing side is kept to string comparisons and JSON on purpose: changes made by someone else between two edits are noted, never merged, since the app does the merging. The record reaches disk before the edit, and edits to one note take turns. [mcp] review_agent_edits in config.toml turns recording off. Records move with their notes on rename, move and archive, and go when a note is deleted or Trash is emptied.
ZenNotes desktop 2.68.0 rewrote every long dash (U+2014) in the text a user reads, because it reads as machine-written. zn carries copies of three of those texts, and they change with it word for word: the MCP server's instructions and its tool descriptions, which assistants show to people, and the built-in templates. The Meeting Notes and 1:1 templates now title new notes "Meeting 2026-10-12" and "1-1 2026-10-12"; notes created before keep their names. Two lines of zn's own output change as well: `zn server status` prints "home 2.68.0 at http://127.0.0.1:7878", and installing or updating a server ends with "home: install complete (version 2.68.0, <url>)".
renovate Bot
added a commit
to scottames/copr
that referenced
this pull request
Oct 13, 2026
This PR contains the following updates: | Package | Update | Change | |---|---|---| | [ZenNotes/zennotes](https://redirect.github.com/ZenNotes/zennotes) | minor | `2.66.0` → `2.68.0` | --- ### Release Notes <details> <summary>ZenNotes/zennotes (ZenNotes/zennotes)</summary> ### [`v2.68.0`](https://redirect.github.com/ZenNotes/zennotes/releases/tag/v2.68.0): ZenNotes v2.68.0 [Compare Source](https://redirect.github.com/ZenNotes/zennotes/compare/v2.67.0...v2.68.0) ZenNotes 2.68.0 lets you review what an AI assistant changed in a note, one change at a time, and keep or undo each. It runs natively on Windows on ARM, makes `zennotes://` links work on Windows, which lets Windows finish connecting ZenNotes Cloud, and stops Tab from turning a heading into a code block. Released from [`881baa6a`](https://redirect.github.com/ZenNotes/zennotes/commit/881baa6a94a441dbf03e59ce6d8d1277624803cf) through [#​930](https://redirect.github.com/ZenNotes/zennotes/pull/930) on 2026-10-12. All installers are verified. #### New - **Review an assistant's edits.** When an assistant you connected through MCP (Claude Code, Codex and others) changes a note, ZenNotes keeps what the note said before. The note shows a banner, "Claude Code changed this note 4 minutes ago", and **Review changes** shows every change right in the note: the removed lines above the new ones, with **Accept** and **Reject** on each, and **Accept all**, **Reject all** and **Done** on top. Reject puts the old text back. What you typed after the assistant is yours and stays out of the review. Move between changes with Cmd+Option+↓ and ↑ (Ctrl+Alt on Windows and Linux), accept with Cmd+Shift+Enter and reject with Cmd+Shift+Backspace; in Vim mode, Vim's own diff keys: `]c` and `[c`, `dp` to keep a change and `do` to put back what it replaced. The command palette lists every note waiting for review. To tell the assistant why, comment on the change before you decide it: assistants read comments through MCP. The kept copy lives beside the note in `.zennotes/agent-edits/`, syncs with your vault, and is deleted once every change is decided. Settings → MCP → **Review agent edits** turns it off. Not covered yet: vaults on a self-hosted server, new notes an assistant creates, and moves, renames and deletions (Trash keeps those). Thanks to Kevin for the idea. - **Windows on ARM** ([#​928](https://redirect.github.com/ZenNotes/zennotes/issues/928)). ZenNotes now has a native build for ARM PCs (Snapdragon X and other Windows on ARM machines): `ZenNotes-2.68.0-win-arm64.exe`, and a zip. Until now those PCs ran the x64 build through Windows' emulation, which costs speed and battery. The download section on zennotes.org lists both, and Edge or Chrome on an ARM PC offers the ARM64 installer by itself. An ARM64 copy updates itself on its own build. An x64 copy that finds itself on an ARM PC moves to the native build with its next update after 2.68.0; to move today, run the ARM64 installer over it (your notes and settings stay, as with any update). Thanks to [@​redanthrax](https://redirect.github.com/redanthrax) for the request. - **What’s New after every update.** The first launch after an update opens a short window: the version’s highlights, ZenNotes Cloud (left out once you use Cloud), and Full release notes on zennotes.org. Escape or Close dismisses it, and What’s New in ZenNotes in the command palette (or `:whatsnew` in Vim mode) brings it back. - **An anonymous count of installs and updates.** So we know how many copies of ZenNotes are in use, the desktop app tells zennotes.org, once when it is installed and once per update: installed or updated, the version, the operating system (macOS, Windows or Linux), the architecture (x64 or arm64) and how it was installed (dmg, installer, AppImage, deb and so on). That is the whole message: no identifier, nothing about your notes, vaults or account, no cookies, no language, and the site keeps only daily totals. It is on by default; Settings → About → Count this copy anonymously turns it off (`[privacy] usage_count = false` in config.toml). The phone apps send nothing of the kind. #### Fixes - **`zennotes://` links open ZenNotes on Windows, and connecting ZenNotes Cloud finishes there** ([#​509](https://redirect.github.com/ZenNotes/zennotes/issues/509)). No Windows install of ZenNotes could open a `zennotes://` link: the installer and the zip never registered the link type, and the app registered it itself only on macOS. Links from an AI answer (the MCP server's note links) or a web page did nothing, Windows offered to "Get an app to open this 'zennotes' link", and connecting ZenNotes Cloud stalled at its last step, which hands the sign-in back to the app through that link. ZenNotes now registers `zennotes://` for your Windows user every time it starts, so links open the note whether the app is running or not (the browser asks once whether to open ZenNotes, as it does for any app). Connecting ZenNotes Cloud on Windows and Linux no longer needs the link at all: after you sign in, the browser returns to ZenNotes through a one-time page on `127.0.0.1` that says "ZenNotes is connected". Thanks to [@​JohannesSterba](https://redirect.github.com/JohannesSterba) for the report. - **Indenting no longer turns a heading into a code block** ([#​925](https://redirect.github.com/ZenNotes/zennotes/issues/925)). Tab indented a heading line like any other line, and in Markdown a heading indented four spaces is a code block, so one press at the default tab size of 4 (two at a tab size of 2) silently turned a heading into code: it lost its styling, its place in the outline and its fold arrow, in Edit and in Preview. Indenting now leaves heading lines at the margin: `## Title` headings, titles underlined with `===` or `---`, and headings inside list items. The rest of a selection still indents as before. When a press moves nothing, a short notice says why. The same goes for Vim's `>>`, `>` and insert-mode Ctrl+T, and the indent button on the phones' editing toolbar. Shift+Tab is unchanged, so a heading indented by hand can still come back. Thanks to [@​uNyanda](https://redirect.github.com/uNyanda) for the detailed report. - **Table column widths carry into Preview** ([#​920](https://redirect.github.com/ZenNotes/zennotes/issues/920)). The widths you set by dragging a column border in the editor did reach Preview, but Preview squeezed the table into the reading column whenever the widths added up to more than it, so every column came out narrower than you set it and the cells wrapped again (Reading width tops out below Editor width, so a table that fit the editor could overflow Preview). A table with set widths now keeps them in Preview and split view, and scrolls sideways when it is wider than the column, the way the editor's table does. The editor had the same squeeze once a table outgrew it, and now scrolls there too. A PDF still shrinks a wide table to fit the page. Reading width now goes up to 1600 px, like Editor width. Thanks to [@​theintjengineer](https://redirect.github.com/theintjengineer) for the report and the videos. - **Plainer wording, and the demo tour's notes renamed.** The app's own text (Settings, the command palette, the in-app manual, notices, the welcome note, the comments in `config.toml`, the `zn` CLI's help and what the MCP server tells your assistant) now uses commas, colons and parentheses instead of long dashes. Two names change with it: the demo tour's notes are now `00 Start Here`, `01 Markdown Basics` and so on, and the Meeting Notes and 1:1 templates name new notes `Meeting 2026-10-12` and `1-1 2026-10-12`. A demo tour made by an older version is replaced when you regenerate it (no second copy) and removed by Remove Demo Tour Notes; notes you already made from a template keep their names. #### For contributors - Windows link registration: `registerAppDeepLinkProtocol` now runs on Windows as well as macOS (`registersDeepLinkSchemeAtLaunch` in `apps/desktop/src/main/deep-links.ts`) and writes `HKCU\Software\Classes\zennotes` with the command `"<exe>" "%1"` at every launch, which covers the zip wherever it was unpacked and follows the app when it moves. electron-builder's `protocols` option is macOS only, which is why no Windows build had it. Linux keeps the package's `.desktop` file (`MimeType=x-scheme-handler/zennotes`): setting the default at launch would override the user's own `xdg-mime` choice. Not done: the NSIS uninstaller leaves the per-user key behind. - Cloud sign-in return path: packaged Windows and Linux builds pass `callback_url=http://127.0.0.1:<port>/auth/callback` (RFC 8252's loopback redirect, `CloudAuthLoopbackServer`, five-minute lifetime, one use), as development builds already did (`cloudSignInUsesLoopback`). Packaged macOS keeps the `zennotes://auth` callback its signed bundle always registers. zennotes.org already accepted loopback callbacks in production. - Heading indent guard ([#​925](https://redirect.github.com/ZenNotes/zennotes/issues/925)): `headingIndentGuard()` in `packages/app-core/src/lib/cm-heading-indent-guard.ts` is a transaction filter on the `input.indent` user event, which [@​codemirror/commands](https://redirect.github.com/codemirror/commands)' `indentMore` sets, and every indent path uses `indentMore`: Tab (`indentWithTab`), the Vim adapter's `>>`, `>` and Ctrl-T, and the phone toolbar's `indent` command. It drops the insertions on lines whose first non-blank character belongs to an `ATXHeading*` or `SetextHeading*` node, read from the syntax tree, so a `#` line in fenced code or frontmatter still indents, and a list item that opens with a heading (`- ## Topic`) still nests. It ships inside `noteMarkdown()`, so every note editor has it; the template editor builds its own `markdown()` and adds it by hand. The notice is an `info` toast, added only when none is already showing. Not changed: ZenNotes' outline, folding, level chips and heading motions read only headings at the margin (`^#{1,6}\s`), although CommonMark accepts up to three spaces, so a heading indented by hand is still a heading in Preview but not in those. - Agent edit review (design and decisions: `docs/ideas/agent-edit-review.md`): - Records: `packages/shared-domain/src/agent-edits.ts` (format, `beginAgentEdit` / `finishAgentEdit`, and the merges: `agentEditOrigin`, `agentEditBaseline`, `reviewedAgentEdit`). Writers stay at string comparisons because two engines write: `apps/desktop/src/mcp/agent-edit-recorder.ts` (TypeScript MCP) and ZenNotes/tui `internal/mcp/agentedits.go` with `internal/vault/agent_edits.go` (the Go `zn mcp` a managed install runs). The record reaches disk before the edit; edits to one note take turns. - Files: `apps/desktop/src/main/agent-edit-files.ts` (Electron-free, shared by main and MCP). Records travel with notes in `relocateNote`, folder renames, deletes, both trashes and creation, in desktop main, the TypeScript MCP and the Go vault; Cloud sync carries `.zennotes/agent-edits/*.json`; the watcher reports them as a new `agent-edits` change scope (path = the note). - Bridge: `supportsAgentEditReview` plus optional `listAgentEdits` / `readAgentEdit` / `writeAgentEdit` (desktop only for now; IPC `vault:list-agent-edits` and friends, vault root from main as always). - Review mode: `packages/app-core/src/lib/cm-agent-review.ts` on `@codemirror/merge` (new dependency, MIT), imported on demand through `agent-review-runtime.ts`; the renderer chunk rule keeps `@codemirror/merge` out of `vendor-editor`, so nothing is added to launch. The pane side is `components/AgentEditReview.tsx` (banner, bar, `useAgentEditReview`). Vim's `dp` / `do` cannot be codemirror-vim mappings (a full match on the `d` operator always wins), so review mode reads normal-mode sequences ahead of Vim. - Settings: portable pref `reviewAgentEdits`, `[mcp] review_agent_edits` in `config.toml` (new `mcp` section), read directly by both MCP engines. - Keys: `editor.reviewNextChange`, `editor.reviewPreviousChange`, `editor.reviewAcceptChange`, `editor.reviewRejectChange` and `vim.review*` in the keymap registry and catalog. - MCP no longer writes into `.zennotes`: `write_note`, `append_to_note`, `prepend_to_note`, `insert_at_line` and `replace_in_note` wrote the file before checking it was in a note folder, so a call on `.zennotes/...` created the file and then failed. Both engines now check first (`noteForWrite` in `apps/desktop/src/mcp/vault-ops.ts`, `Vault.WriteNote` in the Go vault). The self-hosted server's own write path (ZenNotes/znserver) was not checked here. - Windows ARM64 ([#​928](https://redirect.github.com/ZenNotes/zennotes/issues/928)): `release.yml` gains a "Windows arm64" job on GitHub's `windows-11-arm` runner (free for public repos, like `ubuntu-24.04-arm`), running the new `npm run dist:win:arm64 --workspace @zennotes/desktop` (a named script, because PowerShell's `npm.ps1` shim can swallow a `--` before `--arm64`). electron-builder names every Windows feed `latest.yml` whatever the architecture, so the collect step renames the ARM64 job's to `latest-arm64.yml`, and either Windows job fails if its output carries the other architecture's file names (the two jobs upload to one release). The app reads that feed through electron-updater's channel: `windowsUpdateChannel()` in `apps/desktop/src/main/updater.ts` answers `latest-arm64` on Windows when `process.arch` is `arm64` or `app.runningUnderARM64Translation` is true (an x64 copy under emulation, the Windows twin of what electron-updater does for Rosetta on a Mac), and `allowDowngrade` is put back to false because setting a channel turns it on. Nothing native ships in the app (no `.node` files; font-list shells out to scripts), and Windows bundles no `zn`, so the package needed no other change. CI's build matrix adds `windows-11-arm`, which also packages the ARM64 app and runs the new `tooling/scripts/packaged-launch-check.mjs --expect-arch arm64` (a CDP page target, the app drawn, and AArch64 in the executable's PE header): no maintainer has an ARM64 Windows machine, so that step is the proof the build starts. Website (`website/docs-2.68`): `/download/windows-arm64` (and `win-arm64`), a second row in the Windows panel, and the ARM detection through `navigator.userAgentData.getHighEntropyValues(['architecture'])` (the user-agent string reads x64 on ARM too; browsers without the API keep x64, which also runs on ARM). README lists both installers. - Table widths ([#​920](https://redirect.github.com/ZenNotes/zennotes/issues/920)): `rehypeTableColWidths` (`packages/app-core/src/lib/markdown.ts`) now wraps a table that has a `zen:cols` hint in `div.zen-table-scroll` and moves its `data-source-line` stamp to the wrapper (split scroll sync reads `[data-preview-content] > [data-source-line]`, direct children only). CSS: the wrapper scrolls sideways, the table is `width: max-content` with fixed layout, and `@media print` restores the shrink-to-fit for PDF. In the editor, `.cm-table-wrapper:has(> table.cm-table-fixed)` drops the wrapper's `max-width: 100%` (from v2.4.0, older than [#​294](https://redirect.github.com/ZenNotes/zennotes/issues/294)) and `table.cm-table-fixed` is `width: max-content`, so the add-column rail stays at the table's edge and `.cm-table-widget` scrolls: [#​294](https://redirect.github.com/ZenNotes/zennotes/issues/294)'s own comment promised "scrolls if wide", which that older cap prevented. The Reading width slider goes to 1600 (the store already clamped at 1600). A column left `auto` is still sized by its content, so it can differ slightly between the editor and Preview fonts; a drag sets every column, so resized tables match exactly. Docs: a new in-app help topic, "Set the width of a table column", mirrored on the website's GFM tables row. - What’s New: `packages/app-core/src/lib/whats-new.ts` holds the bundled highlights (one entry per release, written in the release PR; Adib chose bundled over fetched), the permanent Cloud card, and the rules (`whatsNewAtLaunch`: a fresh install records its version and opens nothing; a returning user’s first launch of a new version opens the window, with every entry since the version last seen; a downgrade records and opens nothing). The machine-local pref `lastSeenWhatsNewVersion` makes it once per version, recorded before the window opens. Whether this launch is a returning user’s is read with the first prefs load, so skipping the onboarding quickly does not count. The store’s `showWhatsNewAfterUpdate` runs 1.2 s after the main window mounts; `whatsNewOpen` joins VimNav’s skip list and `COMMAND_OVERLAY_FLAGS`, so j/k scroll the window instead of the notes behind it. Full release notes opens `zennotes.org/releases#v<version>`. Desktop only (`hostKind`). - Anonymous count: the same first launch decides the event (`install` or `update`, never a relaunch or a downgrade) and calls the optional `sendUsageCount` bridge method when the portable pref `usageCount` (`[privacy] usage_count`) is on. `apps/desktop/src/main/usage-count.ts` builds the body (`event`, `version`, `platform`, `arch`, `install`), refuses development builds, `ZEN_PERF` and `CI` runs, other architectures and prerelease versions, and sends each event at most once per run with `credentials: 'omit'`, `user-agent: ZenNotes` and `accept-language: *` (Chromium otherwise adds the system language). The server side (`POST /api/v1/app/usage`, daily totals, the owner console’s Usage page with GitHub download counts) is on the website branch `website/app-usage`, and the privacy page says what is sent. - No long dashes (`aa24d748`): the 325 in user-facing strings were rewritten by hand; code comments, test names and third-party text (Excalidraw, Mermaid, KaTeX) are untouched, and a scan of the built `out/` finds none from our code. Older demo tour names are recognized by `currentDemoTourPath` / `isDemoTourStartPath` in `packages/shared-domain/src/demo-tour.ts`, an exact match on the old separator because `generateDemoTour` and `removeDemoTour` (desktop `vault.ts`) delete what it matches; `demo-tour.test.ts` resolves every tour wikilink against the notes the tour ships. Synced copies: zn's MCP instructions, tool descriptions and templates change word for word in ZenNotes/tui `9650f8d`; the self-hosted server's `internal/vault/demo-tour.json` (ZenNotes/znserver) writes the old names until its next release, which the app handles. - Bundled CLI: zn 0.7.0 (`89798b6c`), its `terminal-release.json` copied byte for byte after it verified against `zn-release-1` (source commit `9650f8d`, protocol 1, all four archives matching `checksums.txt`); the staged darwin-arm64 binary reports `zn v0.7.0`. Its `zn mcp`, which a desktop-managed install runs for assistants, records edits for review the same way as the TypeScript server; a managed `zn` updates itself to 0.7.0 within a day on older desktops too. - Docs: the in-app manual's "Tune indentation and switch notes quickly" section, mirrored on the website (the same section and the Tab row of the keyboard table), and a new "Review an assistant’s edits" section, mirrored in the website's MCP docs, both on `website/docs-2.68`. #### Demos In `docs/releases/v2.68.0/media/` (local), 1080p with captions burned in and a `.vtt` beside each, recorded on the 2.68.0 build with a scratch vault and a real MCP client named `claude-code` driving the app's own MCP server: - [agent-edit-review.mp4](https://redirect.github.com/ZenNotes/zennotes/releases/download/v2.68.0/agent-edit-review.mp4) (23 s): an assistant edits a note through MCP; the banner says which one and when; Review changes shows each change with the old text above the new; Reject puts one back (Cmd+Shift+Backspace), and Accept keeps the others, from the keyboard and with the buttons. - [agent-edit-review-vim.mp4](https://redirect.github.com/ZenNotes/zennotes/releases/download/v2.68.0/agent-edit-review-vim.mp4) (28 s): the same review with Vim mode on: `do` puts the old text back, `]c` moves to the next change and `dp` keeps it; Escape leaves with one change still waiting, and the palette's list of notes to review picks it back up. #### Verification How to test locally ([#​509](https://redirect.github.com/ZenNotes/zennotes/issues/509) needs Windows; the beelink VM `zn-win11` has ZenNotes 2.67.0 installed without a handler, see `~/windows-vm/README.md` there): 1. **Links, before and after.** On 2.67.0, `Start-Process 'zennotes://open?path=Welcome.md'` shows "Get an app to open this 'zennotes' link", and clicking such a link in Edge or Chrome does nothing (the browser console says "the scheme does not have a registered handler"). Install 2.68.0 and start it once: `HKCU\Software\Classes\zennotes\shell\open\command` reads `"…\ZenNotes.exe" "%1"`. Click the link again: the browser asks to open ZenNotes, and the note opens, with ZenNotes running and with it closed. 2. **Cloud connect.** Settings → Cloud → Connect ZenNotes Cloud, sign in on zennotes.org: the browser lands on `127.0.0.1:<port>/auth/complete` ("ZenNotes is connected") and Settings shows the account. Before: the last page's link did nothing and the app waited forever. 3. **Review an assistant's edits.** Build and launch with isolated stores as above, open a note, and in a terminal point an MCP client at the same folder: `zn mcp --vault <folder>` (or the desktop's `apps/desktop/out/main/mcp.js` with `ELECTRON_RUN_AS_NODE=1` and `ZENNOTES_VAULT=<folder>`), then have it call `replace_in_note` and `append_to_note` on the note. Before: the note changed and nothing said so. After: the banner names the assistant, **Review changes** shows both changes inline, Reject puts one back (the file on disk follows), Cmd+Shift+Enter keeps the other, the bar says it is done, and `.zennotes/agent-edits` is gone. In Vim mode, `do`, `]c` and `dp` do the same. 4. **Tab on a heading** ([#​925](https://redirect.github.com/ZenNotes/zennotes/issues/925), any platform). Build and launch with isolated stores: `npm run build --workspace @zennotes/desktop`, then `ZENNOTES_USER_DATA_PATH=$(mktemp -d) ZENNOTES_CONFIG_DIR=$(mktemp -d) npx electron apps/desktop/out/main/index.js`. In a note, put the cursor on `#### Sub one` and press Tab (tab size 4, the default). Before: the line became ` #### Sub one`, a code block in Edit and in Preview. After: the line stays a heading and a notice says "Headings stay at the margin: indented four spaces or more, a heading turns into a code block." Select the heading and the paragraph under it and press Tab: the paragraph indents, the heading stays. In Vim mode, `>>` on the heading does the same. 5. **Windows on ARM** ([#​928](https://redirect.github.com/ZenNotes/zennotes/issues/928)). Without an ARM PC: `npm run build --workspace @zennotes/desktop`, then `npx electron-builder --win dir --arm64 --publish never` in `apps/desktop` (any OS), and `file dist/win-arm64-unpacked/ZenNotes.exe` reads "PE32+ executable (GUI) Aarch64". On an ARM PC: install `ZenNotes-2.68.0-win-arm64.exe`, and Task Manager's Details tab, with its Architecture column turned on, shows ZenNotes.exe as ARM64 (x64 for 2.67.0). On zennotes.org in Edge on that PC, the hero button links `/download/windows-arm64`. 6. **Table widths** ([#​920](https://redirect.github.com/ZenNotes/zennotes/issues/920)). In a note with a table, drag the right border of a column header in the editor well past the editor's width. Before: the other columns shrank to make room, and Preview squeezed the table into the reading column and wrapped the cells. After: the table grows and scrolls sideways in the editor, the `<!-- zen:cols=… -->` line under it records the widths, and Preview and split view draw the same widths with a scrollbar under the table. Export to PDF: the table fits the page. Settings → Typography → Reading width now goes to 1600. 7. **What’s New** (desktop). Run `:whatsnew` (or What’s New in ZenNotes from the palette): the window shows the 2.68.0 highlights and the ZenNotes Cloud card; Set up ZenNotes Cloud lands on Settings → Cloud; Escape closes. The automatic open needs a build whose version is newer than the one last seen: the first launch of 2.68.0 after 2.67.x opens it once, and the next launch does not. 8. **Anonymous count**. Settings → About → Privacy shows Count this copy anonymously, on. A development build never sends (unpackaged); a packaged build sends one `POST https://zennotes.org/api/v1/app/usage` on its first launch after installing or updating. With the switch off, nothing is sent. 9. **Demo tour names.** Palette → Generate Demo Tour Notes: the notes are named `00 Start Here` through `15 Search Backends and Fuzzy Workflows`, and every link in `00 Start Here` opens its note. On a vault holding the 2.67.0 tour, the palette offers Regenerate Demo Tour Notes: afterwards there is one tour, under the new names. Remove Demo Tour Notes clears it either way. Before: the names read `00`, a long dash, `Start Here`. #### Distribution channels - **GitHub release:** installers for macOS (Apple silicon and Intel DMG and zip), Windows (x64 and, new, ARM64 installer and zip) and Linux (x64 and arm64 AppImage, deb, rpm, pacman, tar.gz), with five update manifests: Windows on ARM reads the new `latest-arm64.yml`. - **AUR:** `zennotes-bin` 2.68.0-1 (AUR clone `80d9e9a`, repo `cfecf263`), pinned to `ZenNotes-2.68.0-linux-x64.tar.gz` SHA-256 `07b25a34…dce` (GitHub's own digest for the asset), after the bump script checked the bundled CLI folder is world-readable; [aur-check](https://redirect.github.com/ZenNotes/zennotes/actions/runs/38328619236) passed. - **Nix:** `packaging/nix/release-data.json` lifted from the update workflow ([run 38328629102](https://redirect.github.com/ZenNotes/zennotes/actions/runs/38328629102), bot PR [#​931](https://redirect.github.com/ZenNotes/zennotes/issues/931) closed) as `eedda3ed`; its `desktopHash` is the same digest as the AUR pin, and [nix-build on main](https://redirect.github.com/ZenNotes/zennotes/actions/runs/38328850512) passed. - **nixpkgs:** [NixOS/nixpkgs#572180](https://redirect.github.com/NixOS/nixpkgs/pull/572180), which proposed 2.64.0 -> 2.67.0 and had not merged, now proposes 2.64.0 -> 2.68.0; the source hash comes from the tag tarball, and the same prefetch reproduces the 2.64.0 hash in nixpkgs today. - **Homebrew:** `zennotes` 2.68.0 in the tap (`fa5bc22`), mirrored in `78fdf2d4`; both DMGs were downloaded and their SHA-256 matches the cask and GitHub's digest; `brew style` clean. - **Website:** [ZenNotes/website#73](https://redirect.github.com/ZenNotes/website/pull/73) merged at `b3c38483` with the releases entry and its two clips, the docs for every change, the Windows on ARM download (`/download/windows-arm64`) and the 2.68.0 share viewer, which keeps a table's set column widths in published notes; its main tests and deploy passed, Laravel Cloud's deployment succeeded at 01:22 UTC, zennotes.org/releases serves the entry, one clip matches the local file byte for byte, and the live 2.68.0 and retained 2.65.0 viewer files match their manifests. Earlier this cycle: no long dashes anywhere on the site ([#​69](https://redirect.github.com/ZenNotes/zennotes/issues/69)), one size standard for every box and dark scrollbars ([#​70](https://redirect.github.com/ZenNotes/zennotes/issues/70)), the usage count's endpoint, owner page and privacy section ([#​71](https://redirect.github.com/ZenNotes/zennotes/issues/71)), and a home page screenshot with the renamed demo notes ([#​72](https://redirect.github.com/ZenNotes/zennotes/issues/72)). `npm run verify:channels -- 2.68.0`: every applicable channel serves v2.68.0, now including `/download/windows-arm64` (`ef4115e8`). - **zn CLI:** 0.7.0 ([ZenNotes/tui#7](https://redirect.github.com/ZenNotes/tui/pull/7), tag `v0.7.0`, Homebrew formula `04126ba`), bundled here: its `zn mcp` records an assistant's edits for review, and its text drops the long dash with the app's. - **Server:** [ZenNotes/znserver v2.68.0](https://redirect.github.com/ZenNotes/znserver/releases/tag/v2.68.0) pins the published `web-2.68.0-web.h1c5ca208ca08d773` browser artifact and names the demo tour's notes as the apps do (with the same cleanup of the older names); Docker `adibhanna/zennotes:2.68.0`, `2.68` and `latest` (linux/amd64 and arm64, one digest `cf1b1242…`); README [#​25](https://redirect.github.com/ZenNotes/znserver/pull/25). - **Phones:** iPhone 1.24.0 (40) on the published `core-2.68.0-core.h6e3db1e19bc2b662`, with the heading and table fixes and the renamed demo tour (its own Regenerate and Remove now clean up the older names too); submitted to App Review on 2026-10-13 ([zennotesios#58](https://redirect.github.com/ZenNotes/zennotesios/pull/58), main `496b571`), with the privacy policy URL now on https. Android 1.1.38 (41) on the same core, with the same fixes and the same demo tour cleanup, is merged ([zennotesandroid#110](https://redirect.github.com/ZenNotes/zennotesandroid/pull/110), tag `v1.1.38`, merge `251b4ce` with the same tree as the uploaded bundle) and was sent to Google Play review on 2026-10-13 for a full rollout. #### Release validation Cycle checks: - [#​509](https://redirect.github.com/ZenNotes/zennotes/issues/509) on a clean Windows 11 Pro VM (build 26200, the beelink `zn-win11` container), with the official 2.67.0 installer (SHA-256 `38c1fa86…2653`, GitHub's digest) and a 2.68.0 dev build of `238d6504`'s code: 2.67.0's installer and app left no `zennotes` key anywhere in the registry, Windows answered a link with "Get an app to open this 'zennotes' link", and Edge logged "Failed to launch 'zennotes\://open?path=…' because the scheme does not have a registered handler". With the fix in the installed app (`app.asar` swapped in): the key appeared on first launch; links opened the note in the running app (second-instance hand-off) and started the app cold (Windows passes `zennotes://open/?path=…`, which parses); Edge showed "This site is trying to open ZenNotes" and opened the note; the zip registered its own path; Cloud connect opened `https://zennotes.org/app/connect?…&callback_url=http://127.0.0.1:58368/auth/callback` and completed on Adib's sign-in (QA account), then Disconnect revoked the VM's device. The PowerShell workaround posted on [#​509](https://redirect.github.com/ZenNotes/zennotes/issues/509) was run verbatim on 2.67.0: it wrote the same key, and links opened notes cold and warm. Not run end to end: the workaround's Cloud step on 2.67.0 (the website's "Open ZenNotes" button, then the browser prompt). - Unit tests: `deep-links.test.ts` (19, six new), `cloud-auth-loopback.test.ts` (4) and `cloud-auth.test.ts` (20) pass; the desktop typecheck is clean. - [#​925](https://redirect.github.com/ZenNotes/zennotes/issues/925) in the built app over CDP (isolated stores, MacBook display), with a note holding an ATX `####` heading, a setext heading on each underline, a heading inside a list item and a paragraph. Before the fix, at tab size 2: three Tabs left ` #### Sub one` and Preview drew a code block; two Tabs left ` Setext title` (code block) and ` =============` (the heading became a paragraph) and pushed the list item's heading out of it. After the fix, at tab size 2 and 4 and with Vim's `>>`: every heading line was unchanged on disk, Preview still drew H4, H2, H1 and H4, the editor kept its H4 chip and fold arrow, the notice showed, and the paragraph still indented. Unit tests: 12 in `cm-heading-indent-guard.test.ts` (with the guard disabled, the 7 that test it fail and the 5 that pin unchanged behavior pass); all 3,152 app-core tests and the app-core typecheck pass. Website: `php artisan view:cache` and the DocsPage tests (9, 197 assertions) pass on `website/docs-2.68`. - Agent edit review, end to end in the built app (isolated stores, MacBook display) with a real MCP client named `claude-code` driving the real MCP server process (`out/main/mcp.js`): the record held the note from before both edits and named Claude Code and both tools; the banner appeared; the review showed two changes with the removed line above the new one; Reject by button restored and saved the old line; Mod+Shift+Enter accepted the other; the notice said every change was decided; the record and its folder were deleted; the editor was editable again (19/19 checks). Vim mode: `d` then Escape kept the review, `do` rejected, `]c` moved, `dp` accepted (18/18). After Adib's first look, the change bands run the full width of the editor. Demo clips (`media/agent-edit-review.mp4`, `media/agent-edit-review-vim.mp4`, recorded by `tools/demo-review.mjs` with a real MCP client named `claude-code`): the Vim take reopened a review with one change left, and the merge view's "10 unchanged lines" bar was near-white on the dark theme (it takes its grey from CodeMirror's dark-theme flag, which ZenNotes never sets); now themed in `styles/index.css` (`a8c9d8f1`), re-recorded after the fix. - Unit tests: `agent-edits.test.ts` (15), `agent-edit-recorder.test.ts` (9, including concurrent edits and the `.zennotes` refusal), `cm-agent-review.test.ts` (7, including Vim's `do` / `]c` / `dp`), the Cloud sync allowlist; Go: `internal/vault/agent_edits_test.go` (7, including reading a record as the app writes it and following a rename) and `internal/mcp/agentedits_test.go` (6). Full suites: shared-domain 1,991, app-core 3,159, desktop 1,086, quicklook 15 (no turbo cache), all 8 typechecks; zn `go test ./...` and `go vet ./...` clean. - Windows ARM64 ([#​928](https://redirect.github.com/ZenNotes/zennotes/issues/928)), on this Mac: a cross-build (`electron-builder --win dir --arm64`) gave `win-arm64-unpacked/ZenNotes.exe` and every DLL as AArch64, with no `.node` files and no other executables in the package; the full target build wrote `ZenNotes-2.67.0-win-arm64.zip` and the NSIS ARM64 payload, then stopped where electron-builder needs Wine on macOS to build the uninstaller (a Windows runner does not). `updater.test.ts` (45, three new: native ARM64 and emulated x64 read `latest-arm64`, x64 Windows, macOS and Linux keep their feeds); desktop suite 1,093 and all 8 typechecks pass. `packaged-launch-check.mjs` passed against the dev build here (page target in 0.8 s, app drawn, version read) and refused a non-PE file under `--expect-arch arm64`. Website: `DownloadRedirectTest` and `HomePageTest` (46, 196 assertions, including the fallback to the releases page while the latest release has no ARM64 installer), `view:cache`, and the detection block run in Node for Edge on ARM (ARM64 installer), Edge on x64, Firefox, a refused hint and Safari (all x64 or Mac as before). The release skill's `verify-installers.py` expects `latest-arm64.yml` from 2.68.0 and fails a Windows feed naming the other architecture's installer (still ALL GOOD on 2.67.0). Not run: the `windows-11-arm` CI job (it runs on the first push), and an x64 install upgraded by the ARM64 installer on real hardware (the path is electron-builder's ordinary NSIS upgrade, the one Obsidian's universal installer takes on ARM PCs). - [#​920](https://redirect.github.com/ZenNotes/zennotes/issues/920) in the built app over CDP (isolated stores, MacBook display): the reporter's videos showed the cause (their editor column wider than the 1400 px reading column; Preview squeezed the table and wrapped `hypervisor`). Here, with widths that fit (120/520/90), Edit and Preview already matched; with 300/900/300 the editor drew 182/482/182 before the change. After: 300/900/300 in the editor (the widget scrolls, the add-column rail flush with the table's edge), Preview and split view (the wrapper scrolls), 177/501/177 inside the page under print media; tables that fit are unchanged; a table without widths still fills the column; the scroll-sync stamps sit on the wrappers. Dragging the middle column 500 px gave 120/1020/90 on screen and `<!-- zen:cols=120,1020,90 -->` on disk. `markdown.test.ts` (74, one new), app-core 3,160 and its typecheck; website `view:cache` and DocsPage (9, 197 assertions). - What’s New in the built app over CDP (isolated stores, MacBook display): the palette path on the 2.67.0 dev build (7/7: opens the newest entry, Cloud card for someone not on Cloud, five highlights, focus on Close, Escape closes, Set up ZenNotes Cloud lands on Settings with `data-settings-target="cloud"`); the launch path on a build made as 2.68.0 (8/8: a true fresh install, with no config.toml, opens nothing and records 2.68.0; a returning user who last saw 2.67.0 gets the window by itself; j scrolls it in Vim mode; Enter on Close closes it; the next launch shows nothing); a build made as 2.68.1, which has no entry (3/3: the window still opens with the Cloud card and a pointer to the release notes). The temporary versions were put back to 2.67.0. Found on the way: Vim’s global keys did not know the window was open (j moved the sidebar underneath), and a config.toml marks a returning user, as it does for the onboarding. Unit tests: `whats-new.test.ts` (13), `whats-new-launch.test.ts` (7, the store: count once, the switch, the Cloud card rules, the phones left out). - Anonymous count: `usage-count.test.ts` (7). The bytes on the wire, from Electron’s own `net.fetch` with the shipped request options against a local echo server: the five-field JSON body and headers that are the same for every copy; the capture caught Chromium adding `Accept-Language: en-US`, now overridden with `*`. Suites: shared-domain 1,991, app-core 3,181, desktop 1,100, all 8 typechecks. - No long dashes: all 8 typechecks; shared-domain 1,991; desktop 1,102 (two new tests: Regenerate replaces and Remove deletes a tour under the older names, and both fail with the cleanup disabled); `demo-tour.test.ts` (6, including a middle-dot name left alone); `npm run build --workspace @zennotes/desktop` and a scan of `out/` in every encoding found no long dash from our code (46 inside Excalidraw, Mermaid, Langium, KaTeX, Prettier and the HTML entity tables). zn: `go vet ./...` and `go test ./...` clean, and no long dash left in the repo. Release-time gates on `881baa6a`, in a clean worktree: typecheck 8/8 and test:run 6/6 with no turbo cache (shared-domain 1,991, app-core 3,187, quicklook 15, desktop 1,102), build:prod green, `npm audit --omit=dev --audit-level=high` clean (the same 15 low or moderate as 2.67.0). Pack: Developer ID signed, deep strict codesign OK, bundled `zn v0.7.0` in a drwxr-xr-x `Resources/zn-cli`, the Quick Look extension; packaged launch check: page target and drawn app in 1.6 s, version 2.68.0. Smoke suites vim-editor, sidebar-vim and editor-improvements pass after `81f45cee` (the first run failed five typing checks: What's New opened over the editor for their returning-user profiles). Release PR [#​930](https://redirect.github.com/ZenNotes/zennotes/issues/930): all nine checks green, including the first `windows-11-arm` build, which packaged the ARM64 app and launched it; CodeQL's one alert, in the new launch-check script, was fixed in `881baa6a`. Release run [`3832739`](https://redirect.github.com/ZenNotes/zennotes/commit/38327391209): all six jobs green in about 45 minutes; `verify-installers.py` ALL GOOD on the five manifests (`latest-arm64.yml` new); both DMGs match GitHub's digests, and the Apple silicon app is `Notarized Developer ID` with a valid stapled ticket. ### [`v2.67.0`](https://redirect.github.com/ZenNotes/zennotes/releases/tag/v2.67.0): ZenNotes v2.67.0 [Compare Source](https://redirect.github.com/ZenNotes/zennotes/compare/v2.66.0...v2.67.0) ZenNotes 2.67.0 makes Disconnect in Settings → Cloud end the app's access on ZenNotes Cloud, instead of only forgetting it on this computer. Released from [`58ba24ac`](https://redirect.github.com/ZenNotes/zennotes/commit/58ba24acaf78422b1622418cdbf80dfc2647abfa) through [#​924](https://redirect.github.com/ZenNotes/zennotes/pull/924) on 2026-10-12. All installers are verified. #### Fixes - **Disconnecting ends the app's access on ZenNotes Cloud.** Disconnect in Settings → Cloud only forgot the sign-in on this computer. The device stayed listed under Connected apps on zennotes.org, with a token that still worked, until someone removed it there. Now the app asks ZenNotes Cloud to end this device's access first, then forgets the sign-in. Signing out never waits on the answer for more than five seconds: offline, or with the service unreachable, the app still signs out, and the device stays listed on the website, where **Disconnect** ends its access as before. The iPhone and Android apps get the same in their next updates. #### For contributors - Sign-out revoke: the desktop's `CloudAuthManager` sends `DELETE /api/v1/devices/current` with the stored token before it deletes the token, and the shared `CloudAuthFlow` (`packages/shared-domain/src/cloud-auth-flow.ts`) takes an optional `revoke` dependency so the phone apps do the same. A failure, a 401 (the token was already gone) or five seconds without an answer still signs out. The token goes only to an origin connect would accept, the desktop refuses redirects, and a legacy `zennotes.laravel.cloud` account asks `zennotes.org`, where its token moved. Service: ZenNotes/website `4b8f1cb`. - Ids without `crypto.randomUUID`: `randomUUID()` in `packages/shared-domain/src/random-uuid.ts` makes version 4 UUIDs from `crypto.getRandomValues` where `crypto.randomUUID` is missing (Safari and WebKit before 15.4, so iOS 15.0 to 15.3), and Cloud sync, backup restores, the conflict queue and the portable database and filesystem operations now use it. Nothing changes on the desktop, where Electron has `crypto.randomUUID`; the phone apps pick it up with their next core. #### Verification How to test locally: build and launch with isolated stores, `npm run build --workspace @zennotes/desktop`, then `ZENNOTES_USER_DATA_PATH=$(mktemp -d) ZENNOTES_CONFIG_DIR=$(mktemp -d) npx electron apps/desktop/out/main/index.js`, open a vault, and connect ZenNotes Cloud in Settings → Cloud. 1. **Disconnect.** On zennotes.org, open your account's Connected apps: this computer is listed. In the app, choose **Disconnect** in Settings → Cloud, then reload Connected apps. Before: the computer stayed listed and its token kept working. After: it is gone. 2. **Disconnect offline.** Connect again, turn off the network, and choose **Disconnect**. The app signs out within five seconds; once you are back online, the computer is still listed on the website, and **Disconnect** there ends its access as before. #### Distribution channels - **GitHub release:** installers for macOS (Apple silicon and Intel DMG and zip), Windows (x64 installer and zip) and Linux (x64 and arm64 AppImage, deb, rpm, pacman, tar.gz), with the four update manifests. - **AUR:** `zennotes-bin` 2.67.0-1 (AUR clone `fcfcc00`, repo `3638966c`), pinned to `ZenNotes-2.67.0-linux-x64.tar.gz` SHA-256 `79eea21c…a0dd` (GitHub's own digest for the asset), after the bump script checked the bundled CLI folder is world-readable; [aur-check](https://redirect.github.com/ZenNotes/zennotes/actions/runs/38277700429) passed. - **Nix:** `packaging/nix/release-data.json` lifted from the update workflow ([run 38277657281](https://redirect.github.com/ZenNotes/zennotes/actions/runs/38277657281), bot PR [#​927](https://redirect.github.com/ZenNotes/zennotes/issues/927) closed) as `e1af38b0`; its `desktopHash` is the same digest as the AUR pin, and [nix-build on main](https://redirect.github.com/ZenNotes/zennotes/actions/runs/38277997215) passed. - **nixpkgs:** [NixOS/nixpkgs#572180](https://redirect.github.com/NixOS/nixpkgs/pull/572180), which proposed 2.64.0 -> 2.66.0 and had not merged, now proposes 2.64.0 -> 2.67.0; the source hash comes from the tag tarball, and the same prefetch reproduces the 2.64.0 hash in nixpkgs today. - **Homebrew:** `zennotes` 2.67.0 in the tap (`754b33f`), mirrored in `e4875c50`; both DMGs were downloaded and their SHA-256 matches the cask and GitHub's digest; `brew style` clean. - **Website:** [ZenNotes/website#68](https://redirect.github.com/ZenNotes/website/pull/68) merged at `0c8dfb03` with the releases page entry; its main tests and deploy passed, Laravel Cloud's deployment succeeded at 16:39 UTC, and zennotes.org/releases serves the 2.67.0 entry. The share viewer stays on 2.65.0: the 2.67.0 viewer artifact is published, but nothing a reader sees changed. - **zn CLI:** unchanged; this release bundles 0.6.3, still the newest. - **Server:** [ZenNotes/znserver v2.67.0](https://redirect.github.com/ZenNotes/znserver/releases/tag/v2.67.0) pins the published `web-2.67.0-web.h4db5a15773234ee6` browser artifact (nothing changes for self-hosters); Docker `adibhanna/zennotes:2.67.0`, `2.67` and `latest` (linux/amd64 and arm64, one digest `cda965e9…`). - **Phones:** iPhone 1.23.0 (39) and Android 1.1.37 (40) on the published `core-2.67.0-core.hb828dd60259bc376`, with the same Disconnect behavior (and Cloud sync again on iOS 15.0 to 15.3). iPhone 1.23.0 is waiting for App Review ([zennotesios#57](https://redirect.github.com/ZenNotes/zennotesios/pull/57), main `d9e013d`); Android 1.1.37 is merged ([zennotesandroid#109](https://redirect.github.com/ZenNotes/zennotesandroid/pull/109), tag `v1.1.37`, merge `b863e42` with the same tree as the uploaded bundle) and goes to Google Play review. #### Release validation Cycle checks: - The sign-out revoke, in the built app against a local copy of the website: Disconnect revoked the device and deleted its token; against a server that accepts the connection and never answers, the app signed out after 5.06 seconds having sent the one request. Tests cover the revoke, a failure, the 401, the timeout, the origin check, the refused redirect and the legacy host on the desktop, and the revoke, a failed revoke and a sign-in still pending in the shared flow. - The UUID fallback: tests run with `crypto.randomUUID` removed and check 200 distinct version 4 ids, the ids Cloud sync gives new items and operations, and a backup restore's idempotency key; with the fallback taken out, they fail. Release-time gates on `58ba24ac`: - `npm run typecheck` 8/8 and `npm run test:run` 6/6 with no turbo cache: shared-domain 1,974, app-core 3,140, quicklook 15 and desktop 1,071 tests passed. `npm audit --omit=dev --audit-level=high` is clean (the same 15 low or moderate advisories remain, in dompurify, fast-uri, ip-address, katex, smol-toml and sprintf-js). - `npm run pack`: build:prod passed and the app signed on the first try. `codesign --verify --deep --strict` passed, the log shows electron-builder's "skipped macOS notarization" (CI notarizes), and the app bundles `zn` v0.6.3 in a world-readable `Resources/zn-cli` and the Quick Look extension. Packaged launch check: a page target in 1.6 s reporting 2.67.0. - Smoke suites on the built app: `test:vim-editor` (12 checks), `test:sidebar-vim` (12) and `test:editor-improvements` (19) passed on their first run. - [PR #​924](https://redirect.github.com/ZenNotes/zennotes/pull/924): all nine checks passed on `58ba24ac`; `main` fast-forwarded to it and the annotated tag `v2.67.0` started the release run. - The release run published every platform in one pass ([run 38273452908](https://redirect.github.com/ZenNotes/zennotes/actions/runs/38273452908)): Linux arm64 in 12 minutes, Linux x64 in 15, Windows in 21 and macOS in 27. Each Mac app was notarized once: the log shows electron-builder's "skipped macOS notarization" and then one `[notarize]` pass per architecture. - All four update manifests and the 13 files they name passed size and downloaded SHA-512 verification. The apps in both DMGs passed notarization (`Notarized Developer ID`), staple and strict deep signature checks, report 2.67.0 and carry `ZenNotesQuickLook.appex` and a world-readable `Resources/zn-cli` (the arm64 `zn` reports v0.6.3). GitHub latest is v2.67.0, and `verify:channels -- 2.67.0` passed for Homebrew, AUR, Nix and all seven website download routes. </details> --- ### Configuration 📅 **Schedule**: (in timezone America/Los_Angeles) - Branch creation - Every minute (`* * * * *`) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/scottames/copr). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4xMzQuMSIsInVwZGF0ZWRJblZlciI6IjQ0LjEzNC4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiXX0=--> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The zn half of ZenNotes 2.68.0, released as v0.7.0.
zn mcp(what a desktop-managed install runs for assistants) now keeps what a note said before an assistant changed it, in.zennotes/agent-edits/, the format desktop 2.68.0 reviews (Accept / Reject per change). Same records as the desktop's TypeScript MCP server; moves, renames, trash and deletes carry them along..zennotes(d2a5210): the write tools checked the path after writing; they check first now.zn serveroutput lines are reworded.Tests:
go vet ./...andgo test ./...pass locally.