Use Taze to build one structured update plan, apply compatible ranged updates, and make major-version decisions as a
batch.
-
Resolve the skill directory and save the helper plan from the target repository:
bash <skill-dir>/scripts/run-taze.sh --plan [--include package-a,package-b] > <taze-plan.json>
The JSON plan classifies every discovered update as apply, review-major, review, or skip-fixed. The helper
detects monorepos, includes locked versions during scans, and mirrors Bun minimum-release-age settings. If the
repository uses package-manager age gates or Bun catalogs, read
references/conditional-workflows.md for that active branch only.
-
If --dry-run was requested, present the plan and counts, then stop without changing manifests or lockfiles.
-
Select every ranged minor/patch update marked apply. Never auto-approve a major package by name. Present all
review-major and unknown updates in one decision batch with current version, target version, package role when
discoverable, and relevant migration/release notes. Apply only the majors the user selects.
-
If nothing is selected, report the no-op and stop. If the root manifest uses Bun catalogs, preview the exact selected
catalog transitions from the accepted plan:
uv run <skill-dir>/scripts/update-bun-catalogs.py \
--root <repo> --plan <taze-plan.json> --include package-a,package-b
The preview is read-only. Missing catalog entries, conflicting plan rows, unsupported versions, or a catalog value
that no longer matches the plan fail before writes. The helper does not select upgrades.
-
Before the first manifest or lockfile write, discover and run the repository's standard validation suite against the
existing dependency state. Prefer its advertised aggregate check; otherwise run every exposed dependency-resolution,
build, test, typecheck, lint, formatting-check, codegen-check, and repository-invariant command. Use frozen or
non-writing modes where available, and record the exact commands for the post-bump rerun. Attribute every failure
before deciding whether it blocks. Proceed when an unrelated pre-existing failure is reproducible, can be compared
after the bump, and does not prevent dependency resolution or the checks needed to detect regressions; do not fix it
as part of the bump. Dependency or peer-resolution conflicts, actionable unsafe behavior, or a baseline that cannot
provide trustworthy before/after signal block the bump. In that case, stop with
### ⛔ Dependency bump blocked — baseline unusable and report the exact prerequisite and diagnostics without asking
for redundant authorization. Informational notices such as unavoidable deprecations do not block.
-
Write all selected Taze updates in one command:
bash <skill-dir>/scripts/run-taze.sh --write --include package-a,package-b
-
For Bun catalogs, rerun update-bun-catalogs.py with the same plan and include set plus --write. It atomically
updates every matching default/named catalog occurrence and preserves each existing ^, ~, or empty prefix. Then
run ni so the repository's package manager updates its lockfile.
-
Inspect the manifest and lockfile diff. Rerun the exact baseline commands, plus the narrowest checks that exercise
the updated dependencies and any required migrations. Treat every newly introduced error, type issue, check failure
(including tests, builds, lint, formatting, codegen, and repository invariants), dependency or peer-resolution
conflict, and actionable compatibility or safety warning as caused by the bump unless evidence shows otherwise.
-
Fix every issue caused by the bump, including required source or configuration migrations, while preserving intended
behavior. Do not suppress diagnostics, weaken validation, or change expected behavior merely to make checks pass.
After each fix, rerun the affected check, then rerun the complete recorded suite until it passes. If no clear safe
fix exists within the task's authority, stop with ### ⚠️ Dependency regression decision required. Present all such
issues in one table with the evidence, affected locations, fix and revert options, and likely effects. Do not report
completion until the user chooses, the fix is applied or the offending update is reverted, the lockfile is
regenerated, and the complete suite passes.
Completion requires an attributed, comparison-safe pre-write baseline, a reviewed plan, the retained selected updates, a
regenerated lockfile, no new failure in the recorded suite or dependency-specific checks, and no unresolved issue caused
by the bump. Dry-run completion requires the structured plan and zero writes.
