fix(CI): rm dependencies.yml#3396
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
💤 Files with no reviewable changes (1)
📝 WalkthroughWalkthroughThe Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Note
Replacement coverage already in place via Renovate — no stale references found, safe to merge.
TL;DR — Removes the monthly Dependencies upgrade cron workflow now that Renovate handles the same scope (including pnpm catalogs and the compat-test exclusion).
Key changes
- Delete
.github/workflows/dependencies.yml— drops the scheduledpnpm -F !compat-test up+ auto-PR job; Renovate at/renovate.jsoncovers the same surface continuously instead of monthly.
Summary | 1 file | 1 commit | base: master ← RobinTail-patch-3
Scope parity with Renovate
Before: monthly cron runs
pnpm -F !compat-test upand opens one batched PR viapeter-evans/create-pull-request@v8.
After: Renovate (config:recommended,ignorePaths: ["**/compat-test/**"],postUpdateOptions: ["pnpmDedupe"],minimumReleaseAge: "1 day") trickles smaller PRs continuously.
The built-in pnpm-catalog manager enabled by config:recommended parses the catalogs: blocks in pnpm-workspace.yaml, so the prod, peer.zod, and dev entries the cron used to bump are still covered. The ignorePaths glob mirrors the workflow's -F !compat-test filter, so behavior parity is preserved.
renovate.json · pnpm-workspace.yaml
No stale references in the rest of the tree
Before:
Dependencies upgradeworkflow referenced (or referenceable) from CI/docs.
After: clean removal — nothing else in the repo points at it.
No other workflow uses workflow_call, needs, or workflow_run against this one; the remaining peter-evans/create-pull-request@v8 use is the unrelated weekly headers.yml. README / CHANGELOG / AGENTS / CONTRIBUTING / issue templates / FUNDING make no mention of the monthly cadence, and the manual npm-publish.yml and bump.yml don't depend on it. No CHANGELOG entry needed per AGENTS.md (CI-only change, no public-API impact).
.github/workflows/headers.yml · .github/workflows/npm-publish.yml · AGENTS.md
Behavior shifts worth knowing (non-blocking)
Before: one batched monthly PR, auto-assigned to
robintail.
After: continuous Renovate PRs with default (no) assignees.
The cadence change is generally desirable — smaller, easier-to-review PRs. If you want the same reviewer routing the cron had, adding "assignees": ["RobinTail"] and/or "reviewers": ["RobinTail"] to renovate.json is a one-line follow-up. Worth a quick visual check that recent Renovate PRs are healthy before merging, since this deletion removes the monthly safety net.
Claude Opus | 𝕏

Summary by CodeRabbit