chore(deps): bump next from 15.5.18 to 15.5.22 in examples/nextjs-demo - #105
Merged
Conversation
Closes 8 Dependabot alerts (#100, #108-#114) covering 8 advisories, 3 of them high severity: GHSA-p9j2-gv94-2wf4 (CVE-2026-64645) high GHSA-m99w-x7hq-7vfj (CVE-2026-64641) high GHSA-89xv-2m56-2m9x (CVE-2026-64649) high GHSA-4c39-4ccg-62r3 (CVE-2026-64646) medium GHSA-955p-x3mx-jcvp (CVE-2026-64643) medium GHSA-68g3-v927-f742 (CVE-2026-64648) medium GHSA-4633-3j49-mh5q (CVE-2026-64647) medium GHSA-q8wf-6r8g-63ch (CVE-2026-64644) medium Required floor was 15.5.21; 15.5.22 is the current release. next is a direct:production dependency, so the declared range is raised to ^15.5.22 alongside the lockfile. Leaving it at ^15.5.18 would have kept the vulnerable 15.5.18 permitted by the manifest, with the fix present only in the lockfile snapshot. This matches how Dependabot handled the previous direct-dependency bump here (ce5394a: next ^15.5.15 -> ^15.5.18). Verified: next build succeeds, demo dependency policy check passes.
Ndevu12
force-pushed
the
security/bump-next-15.5.21
branch
from
July 31, 2026 17:22
058833a to
ce0392a
Compare
Ndevu12
added a commit
that referenced
this pull request
Jul 31, 2026
Closes **4 Dependabot alerts** on `playground/yarn.lock` — the last remaining alerts that a version bump can actually fix. | Advisory | CVE | Severity | Alert | |---|---|---|---| | GHSA-fx2h-pf6j-xcff | CVE-2026-53571 | high | #64 | | GHSA-p9ff-h696-f583 | CVE-2026-39363 | high | #19 | | GHSA-v6wh-96g9-6wx3 | CVE-2026-53632 | medium | #65 | | GHSA-4w7w-66w2-5vf9 | CVE-2026-39365 | medium | #21 | ## What changed ```diff - "vite": "^6.3.0", + "vite": "^6.4.3", ``` `vite` is a direct devDependency of the playground, so the declared floor is raised alongside the lockfile rather than pinning only the resolved version — consistent with how `next`, `concurrently`, and the root `vite` were handled in #105 and #106. A `yarn dedupe` follows the bump so no stale duplicate `vite`/`postcss` copy is left behind — the same trap that would have silently kept #119 open in #106. ## Verification - `yarn build` (library) — success - `yarn build` (playground) — success
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.
Closes 8 Dependabot alerts — every open
nextalert onmain, 3 of them high severity.What changed
next15.5.18 → 15.5.22 inexamples/nextjs-demo, in both the manifest and the lockfile:The required floor was 15.5.21; 15.5.22 is the current release.
nextis adirect:productiondependency, so the declared range is raised, not just the lockfile pin. Bumping the lockfile alone would leave the manifest still permitting the vulnerable 15.5.18 — the fix would exist only as a lockfile snapshot rather than as part of the declared contract. This matches how Dependabot handled the previous direct-dependency bump in this repo (ce5394a, which movednext^15.5.15→^15.5.18even though that was also an in-range change).Beyond
nextitself the diff touches only its lockstep@next/*platform binaries — nothing else in the tree moves.Verification
next build— compiled successfully, all 3 static pages generatedyarn verify:demos— dependency policy check passesScope
This is a demo app, not the published library.
rich-text-editor-ndevuships onlydist/and none of these advisories touch its 14 runtime dependencies, so consumers of the package were never exposed. Worth fixing regardless — the demo is public and these were the highest-severity alerts by count on the repo.