node-deps-bumper

Topics in the source

• Node Dependency Bumper
• Adding Dependencies
• Multiple Repositories
• Workflow
• User-Facing Output
• Invariants

Use Taze to build one structured update plan, apply compatible ranged updates, and make major-version decisions as a batch. For a new package or CLI, use the repository's package manager and existing range convention instead of Taze. Installing package@latest and retaining the package manager's resulting ^x.y.z range is allowed. Do not replace a caret range with an exact version merely because it can admit future releases. When an effective package-manager minimum-release-age policy exists, it provides the freshness boundary for candidate versions. In that case, read references/conditional-workflows.md. The committed lockfile and frozen deployment install provide reproducibility. Exact-pin only when the user or repository requires it, a known compatibility constraint justifies it, or the package will run without a committed lockfile and frozen install. When the user names two or more repositories or asks to sync or align dependencies across repositories, read references/multi-repo-alignment.md. It runs the Workflow below per repository and adds shared-target selection, one cross-repository major batch, and per-repository commits. 1. Resolve the skill directory and save the helper p

This is an excerpt. Refer to the complete source and its current requirements.