Conversation
2.51.0 shipped the machinery for running the desktop's zn command through a pinned Go binary with the pin left empty, so the bundled Node engine kept serving. ZenNotes/tui v0.2.0 is published now (commit 909e66c3), with the desktop integration protocol 1 and the note creation metadata contract the desktop already writes, so terminal-release.json pins it: the four desktop targets (darwin arm64 and x64, linux arm64 and x64) by release URL and the archive SHA-256 from the release's checksums.txt. From this version the packaged app stages the verified Go binary at build time and the installed zn runs it; `zn tui` opens the terminal app from the same installation, and ZENNOTES_CLI_ENGINE=legacy keeps the Node engine available for the transition. Windows keeps the Node CLI; it has no pinned target yet. Verified: the terminal tooling tests (12) with this pin, the artifact importer staging all four targets from the published archives with digests matching and the integration probe reporting protocol 1 and version 0.2.0, and the compatibility probe against the published darwin-arm64 binary (20 of 20 commands matching in both vault layouts, files equal).
…lls, and Vim block edits The in-app manual mirrors the website docs, so the 2.51 changes land here too: the self-hosted image now comes from ZenNotes/znserver, which also ships standalone binaries; a note's creation date is app-owned metadata under .zennotes/note-metadata that follows the note and belongs in backups; Arch installs go through a graphical polkit prompt with a manual fallback shown in Settings > About; and Ctrl+V block edits apply to every row.
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.
Release branch for ZenNotes 2.51.1, the follow-up to 2.51.0 that pins the published Go CLI.
Feat(cli): pin Go CLI v0.2.0 for the desktop command:terminal-release.jsonpins ZenNotes/tui v0.2.0 (commit909e66c3) for darwin arm64/x64 and linux arm64/x64 by release URL and checksum. The packaged app stages the verified binary at build time; the installedznruns it andzn tuiopens the terminal app.ZENNOTES_CLI_ENGINE=legacykeeps the Node engine during the transition. Windows keeps the Node CLI.Release: align desktop and shared packages at 2.51.1.Verified before the branch: terminal tooling tests with this pin, the importer staging all four targets from the published archives (digests match, probe protocol 1 / version 0.2.0), and the compatibility probe against the published darwin-arm64 binary (20 of 20 commands, files equal). The full ladder,
npm run packwith the staged Go binary, and the packaged CDP smoke run on this branch next; the tag follows them.