Skip to content

ZenNotes v2.90.0

Latest

Choose a tag to compare

@github-actions github-actions released this 20 Nov 22:13
· 3 commits to main since this release

ZenNotes 2.90.0 fixes a creation-date bug on Windows: a note you delete and make again under the same name now gets its own date instead of the deleted note's. The desktop app also bundles zn 0.18.1, which has the same fix, and renders math with KaTeX 0.19.1.

Released from b1895548 through #1101 on 2026-11-20.

Fixes

  • A note made again under a deleted note's name gets its own date on Windows. Windows keeps a deleted file's creation time for about 15 seconds and gives it to the next file created under the same name (NTFS calls this file system tunneling). ZenNotes read a new note's date from the file, so a note deleted and made again right away showed the old note's date, and its first save wrote that date down for good. Every way the app makes a note now records its creation date the moment it makes it: a new note or drawing, an Obsidian drawing conversion, an import, a duplicate, and notes the MCP server creates or duplicates. A note created outside ZenNotes still takes its date from the file. Temporary folder sessions are unchanged and still get no .zennotes/ folder.

  • Math renders with KaTeX 0.19.1. The 0.16 line had a low-severity advisory (GHSA-238p-pmpm-9mq7): prototype pollution already present in a page could turn on KaTeX options the app leaves off. Formulas look the same; equation numbers, matrices, aligned blocks and struck math were checked in Edit and Preview.

zn

  • The desktop app bundles zn 0.18.1 (ZenNotes/tui#55), which records a new note's date the same way, in zn create, zn write, zn capture and zn mcp. A desktop-managed zn already updates itself; this raises the version a fresh install starts from.

Phones

  • iPhone 1.43.0 and Android 1.1.62 carry the shared core of this release. The date fix is for Windows, so the one change there is math rendering with KaTeX 0.19.1.

For contributors

  • startNoteCreation(root, rel) in apps/desktop/src/main/note-creation-metadata.ts is what a creation path calls now, instead of removing the sidecar. It writes {version: 1, createdAt: now} to .zennotes/note-metadata/<rel>.metadata.json atomically (fsynced temp file, then rename) and skips ephemeral roots. zn's writeNoteFileAtomic does the same when the note does not exist yet.
  • Windows CI keeps the tests' scratch vaults on the runner's work disk. os.tmpdir() on a Windows runner is on the C: system disk while the checkout is on D:, and one MCP task update fsyncs four files, which took a 25 ms test past vitest's 5 s limit on a slow runner. The Build job now points TEMP and TMP at RUNNER_TEMP.
  • One KaTeX for the whole tree. rehype-katex, micromark-extension-math and mermaid still ask for katex ^0.16.0, so a root overrides entry moves them to 0.19.1 with everything else. KaTeX 0.18 prefixed its internal classes: an equation number is .katex-tag now, not .tag. A custom theme that styled KaTeX internals needs the new names; .katex and .katex-display are unchanged.
  • The ordered-list tests hand Enter the finished parse. ensureSyntaxTree finishes the parse in the language state's context, but syntaxTree(state) keeps returning the tree the state was created with; an empty transaction (state.update({}).state) adopts the finished one.

Verification

How to test locally, on Windows:

  1. Open a vault in ZenNotes and create a note named Tunnel test. Note the date in its info.
  2. Wait a minute, then delete it permanently (empty it from the Trash).
  3. Within 15 seconds, create a new note named Tunnel test and type a line.
  4. Before: the new note showed the first note's creation date, and kept it after a save and a relaunch. After: it shows the moment you made it, and keeps that after a save and a relaunch.
  5. The same with zn: zn create --title "Tunnel test" --body first, zn delete "inbox/Tunnel test.md" --yes, zn create --title "Tunnel test" --body second, then zn list --limit 1 --json: createdAt is the second create.

Distribution channels

  • GitHub: this release, latest, with all five update feeds. Every file they name was checked, and the app in both macOS DMGs is Notarized Developer ID and stapled.
  • AUR: zennotes-bin 2.90.0-1, pinned to the Linux tarball's SHA-256 b3dbcafd…99b525.
  • Homebrew: the zennotes cask in ZenNotes/homebrew-tap (d2baec7).
  • Nix: packaging/nix/release-data.json (aab158fc), built on main (run 44829703200).
  • nixpkgs: NixOS/nixpkgs#590905, now zennotes-desktop: 2.88.0 -> 2.90.0, waiting for nixpkgs review.
  • Self-hosted server and Docker: unchanged; server 2.84.1 is current.
  • zn: 0.18.1, released first and bundled here; the Homebrew zn formula is on 0.18.1 too.
  • Phones: iPhone 1.43.0 is Waiting for Review on the App Store. Android 1.1.62 is in review on Google Play, and its GitHub release carries Play's signed universal APK. Both carry the shared core core-2.90.0-core.h7d82a7cbcca39312, published as a pre-release.
  • Website: the release page on zennotes.org, zn 0.18.1 on the CLI releases page, and the CLI version in the docs.

Release validation

  • On b1895548: typecheck, every test suite uncached (shared-domain 2715, portable-vault 398, app-core 4949, quicklook 18, web 76, desktop 1964), build:prod, npm run pack and the packaged launch check (page target, rendered, 2.90.0, bundled zn 0.18.1), and the three smoke suites. No hazards, no audit findings at any level, no long dashes.
  • The creation-date fix has tests that fail on the old code, in the app, the MCP server and zn: each fakes NTFS tunneling by handing the recreated file the deleted note's birthtime. It was not run on a real NTFS disk.
  • The gate found two things before the cut. npm audit listed seven low findings, all one KaTeX advisory: KaTeX moved to 0.19.1 everywhere, and math was driven in the built app (inline, struck, numbered, matrices, aligned, underbrace; Edit and Preview) and on both phones. Then one app-core test timed out once under load (a hover preview measured at 190 ms against a 1 s wait); its wait is now 5 s. Every check ran again on the final commit.
  • Windows CI: with the tests' scratch files on the runner's work disk, Windows x64 passed on the first try on both runs of the release pull request and on main, the job that timed out on main after 2.89.0.
  • The phones were walked on the release builds before either store, fresh installs: iPhone 1.43.0 on an iOS 27.2 simulator and Android 1.1.62 on an emulator, with onboarding, a new note, the remote vault step and a note of math. The Android pull request's emulator job could not boot on a runner without hardware acceleration (twice), so the local walk stood in for it. The iPhone Cloud UI tests were skipped (no Cloud change).
  • Not tested before release: packaged Windows and Linux builds beyond CI, and the date fix on a real Windows disk.