Repository navigation
Conversation
next and eslint-config-next move from 16.4.3 to 16.4.6, which clears the Next.js advisory. typescript-eslint now depends on minimatch ^11.0.1 and rimraf on glob ^14.0.3, so the lockfile resolves both to fixed releases on its own and the overrides that pinned them are no longer needed. The exported site is unchanged: every stylesheet is byte-identical and all 32 pages keep the same text, structure, classes and links. Co-Authored-By: Claude Opus 5.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.
nextandeslint-config-next: 16.4.3 → 16.4.6, clearing the Next.js advisory.overrides(minimatch for typescript-estree, glob for rimraf) are removed. Upstream now depends on fixed releases (typescript-estree 8.73.0 → minimatch 11.0.9, rimraf 6.1.4 → glob 14.0.6), and the lockfile resolves them within the declared ranges.npm run checkpasses locally (133/133 tests, visible copy matches the manifest).npm audit --omit=devreports 0 vulnerabilities.Still open:
npm auditreports one remaining advisory, GHSA-fc5q-39xc-vjpf (picomatch ReDoS). It reaches the site only through lint tooling (eslint-config-next→ fast-glob / tinyglobby). It covers every published picomatch release (≤ 4.0.7) and has no patched version yet, so the CI audit step stays red until upstream ships a fix.