v0.1.2

New Features

Post-apply upgrade detection - After successfully applying upgrades, the tool now re-scans for new upgrade opportunities. This catches cases where go mod tidy or yarn install bumps transitive dependencies to new minor versions that have available patch upgrades. If new upgrades are found, you'll see a summary and suggestion to run again.

Go vendor directory support - When a vendor/ directory exists, go mod vendor is now automatically run after go mod tidy to keep the vendor directory in sync with go.mod changes.

CLI Changes

New option:

  -y, --yes    # Skip confirmation prompt and apply upgrades automatically

Bug Fixes

Report files now excluded from git tracking - The patch-upgrades.json and patch-upgrades-summary.md files are now added to .git/info/exclude during operation (alongside the existing *.old backup patterns), preventing accidental commits of temporary report files.

Internal

402 tests, 98% coverage

v0.1.1

Bug Fixes

• Fixed "cannot find main module" error during apply - The backup function was moving files instead of copying them, which caused Go commands to fail because go.mod was temporarily missing. Backups now use copy instead of move, keeping original files in place during updates.

Performance Improvements

• Yarn workspaces: batched lock file regeneration - For yarn workspace monorepos, yarn install now runs once after all package.json files are updated, instead of once per file. This significantly speeds up apply for large monorepos (e.g., 13 packages now runs 2 yarn installs instead of 26).

New Features

• Automatic report cleanup - patch-upgrades.json and patch-upgrades-summary.md are now automatically deleted after successful apply. Use --keep-reports to preserve them.

CLI Changes

New option:

  --keep-reports    # Keep report files after successful apply (default: delete)

Internal

• 385 tests, 98% coverage

v0.1.0.post1

fixed issues with the build/packaging process

v0.1.0

Initial release