build(deps): Bump next from 15.5.14 to 15.5.18 in /site - #25
Closed
dependabot[bot] wants to merge 1 commit into
Closed
build(deps): Bump next from 15.5.14 to 15.5.18 in /site#25dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [next](https://github.com/vercel/next.js) from 15.5.14 to 15.5.18. - [Release notes](https://github.com/vercel/next.js/releases) - [Changelog](https://github.com/vercel/next.js/blob/canary/release.js) - [Commits](vercel/next.js@v15.5.14...v15.5.18) --- updated-dependencies: - dependency-name: next dependency-version: 15.5.18 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
dependabot
Bot
added
dependencies
This was referenced Jul 28, 2026
Owner
|
Superseded by #28, which covers this bump along with the rest of the Dependabot backlog in a single change. Rolling them together was necessary rather than tidy: the |
Contributor
Author
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
DUBSOpenHub
pushed a commit
that referenced
this pull request
Jul 28, 2026
…ctions
npm audit went from 5 high to 0. `npm ci && npx next build` — the exact CI
path — verified clean, with index.html and 404.html in the static export.
Dependencies
- next 15.3.3 -> 16.2.12, which carries patched postcss and sharp
- overrides pinning postcss >=8.5.24 and sharp >=0.35.3, because next 15.5.22
(latest 15.x) still bundles postcss 8.4.31 and sharp 0.34.5
`npm audit fix --force` proposed next@9.3.3 — npm falling back to the last
release without an advisory rather than the first release with the fix. Taking
it would have downgraded four majors to resolve a CVE. Bumping forward is the
actual fix.
Removed eslint and eslint-config-next
Every one of the 9 remaining advisories resolved to a single root: brace-expansion,
reached only through eslint's minimatch@3. There is no patched 1.x — 1.1.16 is the
newest and still inside the advisory range — so the only fix is eslint@10, whose
peer ranges eslint-config-next@16's plugins do not satisfy. Both eslint@10 and an
eslint@9 + brace-expansion override were tried; each crashed the linter outright.
That cost is only worth paying for a working linter, and this one never worked:
no eslint config file has ever existed in this repo, so `npm run lint` has always
exited 2 on a missing config. CI runs `next build` only and never invoked it.
Removing a dependency that has never executed is cleanup, not a capability loss.
Reinstating lint is a clean follow-up once eslint-config-next ships eslint@10
support. Worth noting for whoever picks it up: with a config in place the current
page.tsx reports 8 react-hooks/refs errors, which on inspection are false
positives from react-hooks v7 flagging valid `ref={obj.ref}` usage.
Actions
- pages.yml was using mutable @v3/@v4 tags while validate.yml was SHA-pinned per
the convention set in #11; pages.yml is now pinned to match
- checkout v7.0.1, setup-node v7.0.0, upload-pages-artifact v5.0.0, deploy-pages v5.0.0
- every SHA verified against the tag it claims via the GitHub API
- Pages runner node 20 -> 22; node 20 reached EOL in April 2026 and next 16
requires >=20.9.0
tsconfig.json changes are next 16's automatic migration (jsx react-jsx, dev types
path), applied by the build itself.
Supersedes #21, #22, #24, #25, #26.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 9cb0b232-bb14-47a5-a150-00e71bdddcae
DUBSOpenHub
added a commit
that referenced
this pull request
Jul 28, 2026
npm audit went from 5 high to 0, verified from a clean install off the committed lockfile. - next 15.3.3 to 16.2.12, plus overrides for postcss and sharp. Every 15.x release including the latest still bundles postcss 8.4.31 and sharp 0.34.5, so staying on 15 could not clear the alerts. - Removed eslint and eslint-config-next. All remaining advisories traced to brace-expansion via minimatch 3, which has no patched 1.x. The only fix is eslint 10, which eslint-config-next 16 does not support. No eslint config file has ever existed in this repo, so npm run lint has always exited 2 and CI never invoked it. - pages.yml pinned to SHAs to match validate.yml. Every SHA verified against the tag it claims. Runner node 20 to 22. npm audit fix --force proposed next@9.3.3, npm falling back to the last release without an advisory rather than the first with the fix. Rejected. Supersedes #21, #22, #24, #25, #26. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 9cb0b232-bb14-47a5-a150-00e71bdddcae
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.
Bumps next from 15.5.14 to 15.5.18.
Release notes
Sourced from next's releases.
Commits
9ff92cev15.5.1800ebe23[backport] Disable build caches for production/staging/force-preview deploys ...62c97abv15.5.17423623aTurbopack: Match proxy matchers with webpack implementation (#93594)fa78739Turbopack: Fix middleware matcher suffix (#93590)36e62c6[backport] Turbopack: more strict vergen setup (#93588)36589b5[backport][test] Pin package manager to patch versions (#93596)ad6fd4ev15.5.1679d7dffIgnore malformed CSP nonce headers (#103)c4f6908router-server: guard upgrade proxy against absolute-url SSRF (#77) (#102)Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for next since your current version.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.