chore(renovate): group i18next and react-i18next #333
No reviewers
Labels
No labels
dependencies
major
security-pin
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
trails-cool/trails!333
Loading…
Reference in a new issue
No description provided.
Delete branch "renovate-group-i18next"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
Adds an
i18nextgroup torenovate.json5soi18nextandreact-i18nextarrive in one PR, majors included. The rule sits after the majors →groupName: nullrule, like thereact-routerandvitestgroups.Why
react-i18next@18declarespeerDependencies: { i18next: ">= 27.0.1" }. Renovate opened the two majors separately:^26.3.6, an unmet peer that CI does not check.CI / Checksfor a real reason: i18next 27 tightenedTFunction, so it no longer assigns to the hand-written(key, opts?) => stringparameter ofsummary()inapps/journal/app/routes/notifications.tsx(TS2345).Expected effect
On its next run Renovate closes #331 and #332 and opens one combined PR. That PR will still fail
Checksuntil thesummary()parameter type is fixed — this change makes the PR honest, it does not make the major pass.Testing
Config-only change.
renovate.json5parses as JSON5; the local typecheck/lint/test/e2e suite was not run because no code is touched.🤖 Generated with Claude Code