chore: take the development bumps dependabot could not rebase - #272
Merged
Conversation
#262 and #264 went conflicted when the audit fix touched package.json and the lockfile, and dependabot did not pick them back up — so their checks kept running against the broken base and kept failing on an advisory that main no longer has. Same versions, applied on top of the fix: eslint-plugin-simple-import-sort 12.1.1 → 14.0.0 tsx 4.19.2 → 4.23.12 eslint 10.8.0 → 10.8.1 turbo 2.10.8 → 2.10.10 simple-import-sort crossing two majors is the one worth a look rather than a shrug, since it decides whether a whole codebase's import order still lints. It does: 62/62 turbo tasks, database-backed tests included.
This was referenced Aug 18, 2026
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.
Replaces #262 and #264.
Both went
DIRTYwhen #266 touchedpackage.jsonand the lockfile, and dependabot did not pick them back up after being asked. Their checks kept running against the old base, so they kept failing on the advisorymainno longer has — which would have looked like the bumps' fault indefinitely.Same versions, applied on the fixed base:
eslint-plugin-simple-import-sorttsxeslintturbosimple-import-sortcrossing two majors is the one that deserved checking rather than a shrug — it decides whether every import block in the repo still lints, and lint is a required check. It does, unchanged.Build, typecheck, lint and the full test suite against a live Postgres.