Repository navigation
build(deps): Bump next from 15.5.24 to 16.3.8 - #6634
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [next](https://github.com/vercel/next.js) from 15.5.24 to 16.3.8. - [Release notes](https://github.com/vercel/next.js/releases) - [Commits](vercel/next.js@v15.5.24...v16.3.8) --- updated-dependencies: - dependency-name: next dependency-version: 16.3.8 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
|
|
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. |
There was a problem hiding this comment.
sparq engine
Details
| Benchmark suite | Current: 870c061 | Previous: 674f50b | Ratio |
|---|---|---|---|
store_bytes_per_triple |
88 bytes |
88 bytes |
1 |
dict_bytes_per_term |
53 bytes |
53 bytes |
1 |
comp_store_bytes_per_triple |
44 bytes |
44 bytes |
1 |
store_bytes_per_triple_small |
88 bytes |
88 bytes |
1 |
wasm_bundle_bytes |
1562916 bytes |
1562916 bytes |
1 |
This comment was automatically generated by workflow using github-action-benchmark.
Bumps next from 15.5.24 to 16.3.8.
Release notes
Sourced from next's releases.
... (truncated)
Commits
b0fad0dv16.3.8719e4c6[lts-active] Scope response cache keys to their source route (#218)e92db45[lts-active] Fix metadata propagation for deduplicated nested caches (#223)40c2ba9[lts-active] Match Next data paths case-sensitively (#196)2d9f50a[lts-active] Fix MCP middleware DNS rebinding (#213)bd9214f[lts-active] Fix draft mode leaks through cross-request'use cache'dedupli...8db4a62[lts-active][webpack] EnsuredynamicParamsis respected in `opengraph-image...e002ad6[lts-active] fix(next/image): Pin DNS resolution when fetching external image...4c20699v16.3.72521aec[backport] turbo-tasks-backend: fix strongly consistent read hanging on a can...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)