Repository navigation
chore(renovate): park breaking Rust updates behind dashboard approval - #2583
Merged
Merged
Conversation
A year of 0.x drift surfaced at once (rusqlite 0.32->0.40, tower 0.4->0.5, rand 0.9->0.10, lz4_flex 0.11->0.14, …) plus the Cargo majors. Each needs real porting work that isn't happening this week. dependencyDashboardApproval keeps them listed on the dashboard with a checkbox instead of open PRs: nothing hidden, nothing demanding attention. Tick a box when there's time and that crate gets its PR. JS/actions updates and the safe non-major group are unaffected. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This was referenced Jul 24, 2026
fasterthanlime
added a commit
that referenced
this pull request
Jul 24, 2026
…s get PRs (#2585) Makes renovate leave the PR list alone. #2583 parked breaking **Cargo** updates behind dashboard approval; this extends the same rule to **every major in every ecosystem** (typescript 7, eslint 10, vitest 4, pnpm 11, uuid 14, actions/*@v7, …) and closes the gap that let `update rust` reopen as #2584. Steady state becomes **two PRs, both safe by construction**: 1. the rolling "all non-major dependencies" group, 2. Monday lockfile maintenance. Everything breaking sits on the Dependency Dashboard with a checkbox. Nothing is hidden; nothing demands attention. Tick a box, get that PR. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
pull Bot
pushed a commit
to gaetschwartz/facet
that referenced
this pull request
Jul 24, 2026
…s get PRs Extends the Cargo parking to all ecosystems. Majors are never urgent and always need a human decision, so they belong behind a dashboard checkbox rather than in the PR list. Also closes the toolchain gap that let 'update rust' reopen after facet-rs#2583. Steady state is now two PRs, both safe by construction: the rolling non-major group, and Monday lockfile maintenance. Everything else waits until someone ticks a box. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
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.
Follow-up to #2567. The ungrouping worked — which is how we learned there are 20 breaking Rust updates waiting (14 Cargo 0.x + 5 majors + toolchain): about a year of drift. rusqlite is 8 breaking releases behind; tower, rand, sha2, base64, quick-xml all need porting work.
That work isn't happening this week, and 20 open PRs is noise.
dependencyDashboardApproval: truefor Cargo 0.x-minors and Cargo majors lists them on the Dependency Dashboard with a checkbox instead of opening PRs — nothing hidden, nothing demanding attention. Tick a box when there's time and that crate gets its PR.Deliberately not re-grouping them: #2546 proved renovate can't even resolve a lockfile with 15 simultaneous breaking bumps (
renovate/artifactsfailed).Unaffected: JS/action updates and the rolling safe non-major group.
After this lands the 20 open Rust PRs get closed; they reappear on the dashboard as pending-approval entries.
Co-Authored-By: Claude Fable 5 noreply@anthropic.com