fix: resolve remaining dependabot alerts and renovate automerge - #3592
Merged
Conversation
Lock file maintenance PRs were stuck permanently pending on renovate/stability-days: refreshing ~1000 transitive deps means something is always within the 3 day minimumReleaseAge window, so the check never clears and automerge never fires. Override it to null for lockFileMaintenance specifically. Also groups the eslint ecosystem so peer-coupled packages (eslint, typescript-eslint, eslint-plugin-*) move together in future updates, bumps the exact-pinned @babel/* devDependencies past their pinned patch advisory, and bumps next in examples/ssr within its CodeSandbox-template minor line to clear the remaining alerts.
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.
Summary
renovate/stability-days:minimumReleaseAge: "3 days"was inherited bylockFileMaintenance, and refreshing ~1000 transitive deps means something is always inside that window, so the check never clears and automerge never fires. Overridden tonullforlockFileMaintenanceonly.eslintpackageRule grouping so peer-coupled packages (eslint,typescript-eslint,eslint-plugin-*, etc.) move together in future Renovate updates.@babel/core/@babel/plugin-transform-runtime/@babel/preset-env/@babel/preset-reactdevDependencies to 7.29.7, clearing the one remainingpackage-lock.jsonDependabot alert (lock file maintenance couldn't touch these since they're exact-pinned, not transitive).nextinexamples/ssrfrom 15.5.10 to 15.5.22, staying within the CodeSandboxnextjstemplate's15.5.xline per the existing exception precedent (90156e98), clearing the 24 opennextDependabot alerts. Documents this exception explicitly in.github/copilot-instructions.md.Companion PRs #3469 (lock file maintenance) and #3542 (eslint monorepo to v10) have already been merged directly, which cleared the bulk of the
package-lock.jsonalerts (23 down to 1).Test plan
npm test(check:format, check:types, lint, build, all jest configs across the React version matrix) passesnpm auditshows 0 vulnerabilities against the shippeddependencies; remaining 20 high-severity findings are dev-only, fromjest/ts-jest's own transitiveglob/test-excludepins ofbrace-expansion(GHSA-mh99-v99m-4gvg) - not yet a Dependabot alert, and not fixable without an upstream jest/ts-jest change (confirmed: bumping both to latest patch does not resolve it)cd examples/ssr && npm install && npm run buildsucceeds on next 15.5.22renovate/stability-days: success(or no status at all) and merges without manual intervention