Changelog.
Every release, newest first — written out of the same appcast the app itself reads to find updates. Older builds stay listed and stay downloadable.
What's new
A genuinely native Mac app. The desktop has been rebuilt in SwiftUI and AppKit, preserving Monogrove's visual character and complete workflow while replacing Wails, React, and WebKit.
Native interaction throughout. Large package and project collections are virtualized, the project picker behaves as a keyboard-accessible tree, update confirmation is a proper window sheet, and the split view uses native resizing and accessibility actions.
A hardened Go helper. The scanner, updater, CLI, and TUI remain Go, now connected to the app through a private, versioned, strictly validated protocol.
A more legible terminal UI. The TUI now uses a role-based adaptive palette, clearer hierarchy, responsive columns and histogram scaling, and shapes as well as colour for status.
Improvements
Scanning uses bounded workers, parses shared lockfiles once, cancels superseded work promptly, and defends workspace and mutation paths against traversal and symlink escapes.
Reviewed update plans are consumed atomically, package-manager process trees are terminated on cancellation, and helper failure during an update is reported as an unknown outcome instead of being replayed.
Progress is coalesced for a responsive interface, with improved contrast, Reduce Motion and Reduce Transparency support, complete accessible names, and deliberate VoiceOver announcements.
The project picker prebuilds an immutable search index, keeping 10,000-project searches within the 50 ms p95 interaction budget.
The app and bundled helper are universal arm64/x86_64 binaries, signed with Developer ID, notarized, and stapled by Apple.
Native focus restoration and helper-team verification are covered by release-only tests, including keyboard-only confirmation and real Security.framework signature inspection.
Notes
Monogrove 0.3.0 requires macOS 26.0 or later. The Go CLI and TUI remain available, and all older release artifacts remain unchanged.
What's new
pnpm catalog support. Dependencies using the catalog: protocol are detected, shown with a catalog tag, and updated by editing pnpm-workspace.yaml once — preserving your comments, quoting, and formatting — then reinstalling. One update covers every consumer, keeps the range operator, and never de-catalogs a dependency into a pinned version.
Grouping folders. Repos nested one level under a folder (e.g. ~/Sites/material-bank/*) are now detected instead of silently skipped, and appear as collapsible folder groups in the project picker — visually distinct from monorepos.
"Current range" update strategy. A new default that moves each dependency to the newest version its package.json range already allows, alongside Latest and Next-major.
Improvements
Project-picker redesign: folders and monorepos share one collapse interaction, with a small kind icon (folder vs. monorepo) beside the package-manager tag.
Dependencies updated across the app (React 19, Vite 8, TypeScript 6, Go modules) and the marketing site (Next 16.2.10), clearing all known npm advisories.
Notes
Catalog updates run through the desktop app; the standalone CLI update path is unchanged this release.
What's new
Bulk update across multiple projects. Filter the workspace to the folders you want, then hit "Update all" to dry-run every outdated dependency in one go — review the plan, confirm, run.
Multi-project updates require an explicit "I understand" confirmation with a short countdown before any commands execute. Single-project and per-package updates are unchanged.
Project picker shows a loader during refresh, so there's no silent dead time after committing a filter change.
What's new
Dependency notes. Monogrove now surfaces lightweight editorial guidance for packages that are deprecated, effectively retired, replaced by stable platform APIs, or commonly swapped for modern alternatives.
Dependency notes are collapsed by default, can be dismissed locally, and can be restored if hidden.
Packages with visible dependency notes now show a small green note icon beside the package name.
Notes
These notes are deliberately not security advisories. They are prompts for future cleanup, written to be easy to ignore when the package is already earning its place.
What's new
Update every package in a folder. Pick a single project (or filter the workspace down to one) and the inspector now offers a one-click Dry run all to latest — every outdated dependency planned, deduped, and presented as a single batch before anything touches disk.
A small All to latest → shortcut in the Update plan header lets you switch from a package-scoped plan to a folder-wide plan without backing out.
Bug fixes
Bun projects no longer show up as NPM. Bun 1.2+ ships a JSONC bun.lock (the older bun.lockb is gone); Monogrove now detects both, and also honours the Corepack "packageManager": "bun@x.y.z" field in package.json as the authoritative signal — so even projects with no lockfile yet classify correctly.
No more duplicate plan/result cards for projects that ship multiple targets in the same run.
The missing-package-manager banner collapses repeated failures into one row per affected target instead of repeating the same project name.
Notes
Tags the appcast.xml fetch with an anonymous install-source query parameter (brew, dmg, or dev) so the project can aggregate install-method breakdowns from Vercel access logs. No per-install identifiers and no new endpoints — every install with the same source sends an identical query string.
Bug fixes
Routes Homebrew installs to brew upgrade --cask monogrove instead of opening the release DMG in a browser. Both the in-app update banner and the Check for Updates menu now detect a Homebrew install and offer a one-click copy of the brew command.
Bug fixes
Finds pnpm, yarn, bun, and npm when Monogrove is launched as a Mac app. GUI launches inherit a minimal PATH from launchd, so package managers installed via Homebrew or standalone installers weren't being seen, and every batch update failed with the same opaque error.
Replaces the raw executable file not found error with a friendly per-package-manager install hint pointing at the canonical install command.
What's new
When a package manager isn't installed, the Results panel shows a single banner per missing tool with a count of affected projects, instead of repeating the same error card across every project.
What's new
Adds an About Monogrove item to the app menu so you can see the running app version from a native dialog.
What's new
Adds a package severity dropdown in the sidebar so you can quickly filter to Critical, High, Minor, Patch, or Current package groups.
The sidebar footer now shows package-list context instead of repeating the workspace project count.
Bug fixes
Removes the empty app-update banner spacer when no update is available.
Keeps the severity filter count aligned with the active Outdated / All view.
What's new
Checks npm alias dependencies against their real registry package name, so colorscope: npm:@howells/colorscope@... is resolved as @howells/colorscope.
Reads npm registry configuration and auth tokens from .npmrc / ~/.npmrc for registry metadata checks.
Bug fixes
Fixes private @howells/* package checks for workspaces such as materia.
Shows clearer registry errors when scoped packages may need npm authentication.
What's new
Adds native app menu actions for checking for app updates and installing the bundled monogrove CLI/TUI command into your PATH.
Shows exact registry packages that could not be checked, including the registry error reason.
Sorts package lists by project count so the most widely-used packages stay at the top.
Bug fixes
Reserves red for critical security issues, with amber/yellow/green/grey used for lower-risk update states.
Fixes website font loading, mobile layout polish, and screenshot hydration behavior.
What's new
Bundles the standalone CLI/TUI inside Monogrove.app so Homebrew can install both the Mac app and the terminal command from the same cask.
Bug fixes
Signs the bundled CLI/TUI binary before notarization, fixing release validation for the combined app package.
Release artifacts and checksums live on GitHub Releases.