chore: add a dependency watcher - #3
Merged
Merged
Conversation
23 of 30 repos in the fleet had none. The symptom looks like neglect and is not: aoz-housing had 100 commits in August, features landing daily, and was still on Next 14 / React 18 / Tailwind 3 — because nothing ever OPENED the upgrade PR. Version drift here is the absence of a mechanism. npm directory: /. Minor and patch grouped so the sweep spends one cycle on them; majors stay separate because they deserve reading. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UvjGNAS9CMfEGNW26tUR4P
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
23 of 30 repos in the fleet had no dependency watcher at all.
The symptom looks like neglect and isn't. aoz-housing had 100 commits in August — features landing daily — and was still on Next 14, React 18 and Tailwind 3. Not because nobody touched it, but because nothing ever opened the upgrade PR. Version drift here is the absence of a mechanism, not the absence of attention.
Weekly. Minor and patch are grouped into one PR so the auto-merge sweep spends one cycle on them instead of five; majors stay separate because they deserve to be read. GitHub Actions versions are watched too — that is how a
uses:reference goes stale unnoticed.🤖 Generated with Claude Code
https://claude.ai/code/session_01UvjGNAS9CMfEGNW26tUR4P