chore(deps): bump next from 16.2.6 to 16.2.11 - #3421
Conversation
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. |
@faststore/api
@faststore/cli
@faststore/components
@faststore/core
@faststore/diagnostics
@faststore/lighthouse
@faststore/sdk
@faststore/ui
commit: |
renatomaurovtex
left a comment
There was a problem hiding this comment.
Security-motivated patch bump, safe to take:
- Lockfile-only and in-range: the workspace catalog pins
next: ^16.2.6, so 16.2.11 resolves without touching any manifest.nextis already a runtime dependency of@faststore/core— no new dependency, no Dependency Discipline checklist needed. - The advisories are worth it: 16.2.11 fixes 4 High (DoS via Server Actions, middleware/proxy bypass, 2× SSRF) and 5 Moderate advisories. Several are App Router/Turbopack-specific and don't apply to FastStore's Pages Router setup, but the two cache-confusion-of-response-bodies fixes and the Image Optimization SVG DoS fix are relevant to stores on Pages Router — good reason to merge rather than wait.
- The ±26k line churn is the usual pnpm lockfile reflow, same pattern as #3416/#3418.
- The red FastStore check is only the "Publish to Chromatic" step failing with
✖ Missing project token(dependabot PRs don't get the secret — known pattern, #3361 tracks it). SonarQube and all turbo build/test tasks are green.
Verdict: Approved
Blocking (🔴/🟠):
- None.
Non-blocking (🟡/💬):
- 💬 Red FastStore check = Chromatic token pattern on dependabot PRs, not a regression.
Checks to confirm before merge: none beyond existing CI — lockfile-only.
9404a9e to
f49560e
Compare
03ffa6f to
69d9744
Compare
|
Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting |
1 similar comment
|
Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting |
8528c8b to
866fcbb
Compare
a9dbaa7 to
aa39e29
Compare
b21ec39 to
918ae41
Compare
Bumps [next](https://github.com/vercel/next.js) from 16.2.6 to 16.2.11. - [Release notes](https://github.com/vercel/next.js/releases) - [Commits](vercel/next.js@v16.2.6...v16.2.11) --- updated-dependencies: - dependency-name: next dependency-version: 16.2.11 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
918ae41 to
67b521d
Compare
|

0 New Issues
0 Fixed Issues
0 Accepted Issues
No data about coverage (35.90% Estimated after merge)
Bumps next from 16.2.6 to 16.2.11.
Release notes
Sourced from next's releases.
Commits
9beca08v16.2.113c48c7a[16.x] Fix Turbopack middleware matcher with i18n single localeac1eff3[16.x] Improve performance of checking valid MPA form submissions9a4651e[16.x] EnforceserverActions.bodySizeLimitfor Server Actions in Edge runtimeb512063[16.x] Set correct origin for internal redirects in custom serverd303326[16.x] Ensure exotic rewrite param values are properly encoded73b9487[16.x] fix(fetch-cache): key fetch(Request, init) by the effective requestbf9d17f[16.x] fix(incremental-cache): byte-exact fetch cache key for binary bodiesfe28768[16.x] fix(next/image): improve performance of detectContentType()d8afb8d[16.x] Performance improvements when decoding React Server function payloads