fix-dependabot

From README

Steps Get PR info — Use gh pr view --json headRefName,files,title,body to identify the branch name, which dependency was bumped, and the old/new versions. Checkout the branch: Update all monorepo instances — Dependabot only touches one package. Search for all other package.json files that reference the same dependency at the old version and update them too: Update every match to the new version. Preserve the prefix style (^, , or exact) that each package already uses. Run bun from the repo root to regenerate bun.lock. Verify — Run git status to confirm only bun.lock and the expected package.json files were modified. If other unexpected files changed, investigate before proceeding. Commit and push: Switch back — Return to your previous branch (usually main): Notes Dependabot says "Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself" — but updating the lockfile and sibling packages is the expected workflow and won't cause issues.