You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Records why the ESLint 10 upgrade remains blocked: the current Next ESLint bundle includes React, import, and jsx-a11y plugins whose peer ranges stop at ESLint 9.
Keeps the safe supported toolchain at eslint@9.39.5; does not force peer ranges or run a forced audit fix.
RAG impact: no retrieval behaviour change — documentation only.
Verification
npm run check:runtime — Node 24.18.0 / npm 11.17.0 pass.
npm run check:installed-lock-parity — framework/toolchain versions match the lock.
Installed manifests confirm eslint-plugin-react@7.37.5, eslint-plugin-import@2.32.0, and eslint-plugin-jsx-a11y@6.10.2 declare ESLint support only through 9.x.
npm run check:outstanding-issues — 146 rows, unique IDs, next-id 149.
This pull request has been ignored for the connected project sjrfecxgysukkwxsowpy because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.
Updated the branch review ledger with new and reordered review records, and revised outstanding issue #090 to document the ESLint 10 ecosystem blocker and updated upgrade guidance.
Changes
Documentation ledgers
Layer / File(s)
Summary
Review record synchronization docs/branch-review-ledger.md
Added, reordered, and refreshed documentation-sync, PR review, Playwright cache, issue-ledger, ESLint blocker, and issue correction records.
ESLint blocker status docs/outstanding-issues.md
Updated issue #090 with plugin peer-range limitations, the React plugin crash, revised next steps, stop guidance, and the new date.
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
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
eslint@9.39.5; does not force peer ranges or run a forced audit fix.main, preserving the PR: Production readiness improvements and E2E fixes #105 correction and all other issue-ledger changes.RAG impact: no retrieval behaviour change — documentation only.
Verification
npm run check:runtime— Node 24.18.0 / npm 11.17.0 pass.npm run check:installed-lock-parity— framework/toolchain versions match the lock.eslint-plugin-react@7.37.5,eslint-plugin-import@2.32.0, andeslint-plugin-jsx-a11y@6.10.2declare ESLint support only through 9.x.npm run check:outstanding-issues— 146 rows, unique IDs, next-id 149.npm run check:branch-review-ledger— pass.Risk
Documentation-only. No dependency, runtime, provider, schema, production-data, or deployment change.