npm / taze
taze
What changed in taze 19 to 21, from its official release notes, upgrade guides and advisories. Sources checked 2026-11-13.
3 breaking13 new APIs and options3 performance7 behavior and defaults2 tooling20 fixes and other
See which of these apply to your code, ranked, in your agent:
npx @unstale/cli inittaze 215 changes
Breaking changes 2
Implicit CLI defaults no longer override options specified in the config file.
The project is restructured into manifest and registry axes, with support for custom manifests.
New APIs and options 3
Taze now ships with skills.
GitHub Actions can pin up-to-date tags to SHA using style: 'sha'.
JSR is now supported as a first-class registry.
taze 206 changes
Behavior and default changes 1
Respect DO_NOT_TRACK to disable the third-party metadata endpoint.
Tooling 1
taze can now check and update GitHub Actions in workflows.
Fixes and other changes 4
Preserve default locked updates.
Locked updates stay within the patch range.
Preview versions are now matched correctly for prerelease ranges.
Recent changes now show hours instead of ⩽1d.
taze 1937 changes
Breaking changes 1
The taze usage command was removed; use node-modules-inspector instead.
New APIs and options 10
Taze can resolve custom registries via get-npm-meta v0.3.0.
Updates to devEngines.packageManager are supported.
Adds a flag to output update information as JSON.
Enables and exposes retry behavior for npm metadata fetches.
Environment variable support is added for .npmrc.
A stable version mode is available for selecting versions.
Adds support for package.yaml and dependencies resolution with PNPM.
Exposes a --concurrency option.
Adds support for Yarn catalogs.
taze now supports the overrides field in pnpm-workspace.yaml.
Performance 3
Smooths redraws during interactive rendering.
Reduces flicker during interactive use.
Optimizes rendering time to resolve flickering during interaction with large data.
Behavior and default changes 6
The --exclude option accepts name@range selectors to skip specific versions.
Taze reads pnpm updateConfig ignore lists from pnpm-workspace.yaml.
Taze respects package manager maturity exclusions when selecting versions.
maturityPeriod is now auto-inferred from pnpm or yarn workspace configuration.
The interactive TUI exits when the user presses q.
Supports packageManager values with a hex hash.
Tooling 1
A JSON schema is available for tazerc configuration, enabling schema-based validation and editor support.
Fixes and other changes 16
Handles a missing package manager when displaying the install hint.
Restores the timeout for metadata requests.
Respects
minimumReleaseAge: 0as disabling pnpm release age checks.Corrects parsing of compound version ranges in pnpm overrides.
Avoids falling back to a prerelease as the latest version.
Keeps the version selector visible.
Interactive mode now respects the configured maturity period.
Nested Bun workspaces are ignored.
Locked versions are updated with a mature version.
Version selection handles latest and next tags more appropriately.
Prevents bun catalog writes from being clobbered when running taze -w.
Fixes version resolution.
Preserves comments and formatting in package.yaml.
Fixes a missing concurrency parameter in the CLI's cac integration.
Fixes loading of npm global packages.
Fixes sorting of package globs.