vercel[bot]
commented
4 years ago This pull request is being automatically deployed with Vercel (learn more). To see the status of your deployment, click on the icon next to each commit.
Closed renovate[bot] closed 1 year ago
vercel[bot]
commented
4 years ago This pull request is being automatically deployed with Vercel (learn more). To see the status of your deployment, click on the icon next to each commit.
vercel[bot]
commented
2 years ago Deployment failed with the following error:
should NOT have additional property `type`
codecov-commenter
commented
2 years ago :exclamation: No coverage uploaded for pull request base (
master@12acd7e). Click here to learn what that means. Patch has no changes to coverable lines.
:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.
vercel[bot]
commented
1 year ago The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name | Status | Preview | Comments | Updated (UTC) |
|---|---|---|---|---|
| wowgit | ❌ Failed (Inspect) | Oct 31, 2023 11:05pm |
vercel[bot]
commented
1 year ago Deployment failed with the following error:
The `vercel.json` schema validation failed with the following message: should NOT have additional property `type`Learn More: https://vercel.com/docs/concepts/projects/project-configuration
renovate[bot]
commented
1 year ago Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
The artifact failure details are included below:
npm WARN old lockfile
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: wowgit@0.0.1
npm ERR! Found: react@16.14.0
npm ERR! node_modules/react
npm ERR! react@"^16.4.1" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^17.0.2" from next@11.1.4
npm ERR! node_modules/next
npm ERR! next@"^11.0.0" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /tmp/worker/320349/69ada0/cache/others/npm/_logs/2023-10-31T23_04_29_423Z-eresolve-report.txt
npm ERR! A complete log of this run can be found in: /tmp/worker/320349/69ada0/cache/others/npm/_logs/2023-10-31T23_04_29_423Z-debug-0.log
This PR contains the following updates:
^7.0.2->^11.0.0GitHub Vulnerability Alerts
CVE-2020-5284
Impact
serverlesstargetnext exportWe recommend everyone to upgrade regardless of whether you can reproduce the issue or not.
Patches
https://github.com/zeit/next.js/releases/tag/v9.3.2
References
https://github.com/zeit/next.js/releases/tag/v9.3.2
CVE-2021-43803
Next.js is a React framework. In versions of Next.js prior to 12.0.5 or 11.1.3, invalid or malformed URLs could lead to a server crash. In order to be affected by this issue, the deployment must use Next.js versions above 11.1.0 and below 12.0.5, Node.js above 15.0.0, and next start or a custom server. Deployments on Vercel are not affected, along with similar environments where invalid requests are filtered before reaching Next.js. Versions 12.0.5 and 11.1.3 contain patches for this issue. Note that prior version 0.9.9 package
nexthosted a different utility (0.4.1 being the latest version of that codebase), and this advisory does not apply to those versions.CVE-2021-37699
Next.js is an open source website development framework to be used with the React library. In affected versions specially encoded paths could be used when
pages/_error.jswas statically generated, allowing an open redirect to occur to an external site. In general, this redirect does not directly harm users although it can allow for phishing attacks by redirecting to an attacker's domain from a trusted domain.Impact
10.0.5and10.2.011.0.0and11.0.1usingpages/_error.jswithoutgetInitialProps11.0.0and11.0.1usingpages/_error.jsandnext exportpages/404.jsnextnpm package hosted a different utility (0.4.1 being the latest version of that codebase), and this advisory does not apply to those versions.We recommend upgrading to the latest version of Next.js to improve the overall security of your application.
Patches
https://github.com/vercel/next.js/releases/tag/v11.1.0
Release Notes
vercel/next.js (next)
### [`v11.1.3`](https://togithub.com/vercel/next.js/releases/tag/v11.1.3) [Compare Source](https://togithub.com/vercel/next.js/compare/v11.1.2...v11.1.3) See https://github.com/vercel/next.js/releases/v12.0.5 for details about this patch. ### [`v11.1.2`](https://togithub.com/vercel/next.js/releases/tag/v11.1.2) [Compare Source](https://togithub.com/vercel/next.js/compare/v11.1.1...v11.1.2) ##### Core Changes - chore: upgrade styled-jsx to 4.0.1: [#28626](https://togithub.com/vercel/next.js/issues/28626) - getServerSideProps should support props value as Promise: [#28607](https://togithub.com/vercel/next.js/issues/28607) - Ensure custom app regex is correct for Windows: [#28631](https://togithub.com/vercel/next.js/issues/28631) ##### Credits Huge thanks to [@huozhi](https://togithub.com/huozhi) and [@kara](https://togithub.com/kara) for helping! ### [`v11.1.1`](https://togithub.com/vercel/next.js/releases/tag/v11.1.1) [Compare Source](https://togithub.com/vercel/next.js/compare/v11.1.0...v11.1.1) ##### Core Changes - Next.js swc publish flow: [#27984](https://togithub.com/vercel/next.js/issues/27984) - Ensure config file message is only shown once: [#28017](https://togithub.com/vercel/next.js/issues/28017) - Add missing fields to `NextConfig` type: [#27974](https://togithub.com/vercel/next.js/issues/27974) - use a shared worker pool for collecting page data and static page generation: [#27924](https://togithub.com/vercel/next.js/issues/27924) - Use [@next](https://togithub.com/next) scope for native packages: [#28046](https://togithub.com/vercel/next.js/issues/28046) - Fix `generateBuildId` type that can be async function: [#28040](https://togithub.com/vercel/next.js/issues/28040) - Fix image optimization encoding url: [#28045](https://togithub.com/vercel/next.js/issues/28045) - Clean up `Document` in preparation for streaming: [#28032](https://togithub.com/vercel/next.js/issues/28032) - Render as a concatenation of streams: [#28082](https://togithub.com/vercel/next.js/issues/28082) - Add support for dynamic HTML: [#28085](https://togithub.com/vercel/next.js/issues/28085) - Support suspense in next dynamic: [#27611](https://togithub.com/vercel/next.js/issues/27611) - Handle blob urls in image component: [#27975](https://togithub.com/vercel/next.js/issues/27975) - Bypass webpack compilation for precompiled [@next/polyfills-nomodule](https://togithub.com/next/polyfills-nomodule): [#27596](https://togithub.com/vercel/next.js/issues/27596) - Update `util` to 0.12.4: [#27939](https://togithub.com/vercel/next.js/issues/27939) - Remove duplicate doctypes: [#28089](https://togithub.com/vercel/next.js/issues/28089) - Fix revalidate for initial notFound: true paths: [#28097](https://togithub.com/vercel/next.js/issues/28097) - Add proper error when failing to load next.config.js: [#28099](https://togithub.com/vercel/next.js/issues/28099) - Fix: wrong link error message: [#28127](https://togithub.com/vercel/next.js/issues/28127) - Add support for Jaeger trace target: [#28129](https://togithub.com/vercel/next.js/issues/28129) - Enable pure client suspense in blocking rendering: [#28165](https://togithub.com/vercel/next.js/issues/28165) - Add entrypoint tracing: [#25538](https://togithub.com/vercel/next.js/issues/25538) - Add module type to build-module trace: [#28128](https://togithub.com/vercel/next.js/issues/28128) - Update to latest babel versions: [#28174](https://togithub.com/vercel/next.js/issues/28174) - Improve jaeger traces: [#28168](https://togithub.com/vercel/next.js/issues/28168) - fix development mode bug with pages with "+" and other special characters: [#28122](https://togithub.com/vercel/next.js/issues/28122) - let loaders automatically infer source map setting: [#28204](https://togithub.com/vercel/next.js/issues/28204) - Avoid fs write `next-env.d.ts` on read-only filesystems: [#28206](https://togithub.com/vercel/next.js/issues/28206) - Document usage of suspense option of next/dynamic: [#28210](https://togithub.com/vercel/next.js/issues/28210) - Add warning when parent styles break `next/image`: [#28221](https://togithub.com/vercel/next.js/issues/28221) - Use `zen-observable` library: [#28214](https://togithub.com/vercel/next.js/issues/28214) - Fix HMR when custom \_app or \_document is removed: [#28227](https://togithub.com/vercel/next.js/issues/28227) - Add relationship between issuer and module to traces: [#28192](https://togithub.com/vercel/next.js/issues/28192) - Update generating next-server dependencies: [#28223](https://togithub.com/vercel/next.js/issues/28223) - Fix `next/image` blur placeholder when JS is disabled: [#28269](https://togithub.com/vercel/next.js/issues/28269) - Ensure adding \_app/\_document HMRs correctly: [#28279](https://togithub.com/vercel/next.js/issues/28279) - upgrade webpack to 5.51.1: [#28291](https://togithub.com/vercel/next.js/issues/28291) - \[ESLint] Adds `process.exit` to `next lint` success output: [#28299](https://togithub.com/vercel/next.js/issues/28299) - Fix next env vars injection in dynamic: [#28309](https://togithub.com/vercel/next.js/issues/28309) - Add layout to data-nimg attribute: [#28312](https://togithub.com/vercel/next.js/issues/28312) - Add data attribute to script component: [#28310](https://togithub.com/vercel/next.js/issues/28310) - Ensure [@babel/core](https://togithub.com/babel/core) is de-duped when nccing: [#28384](https://togithub.com/vercel/next.js/issues/28384) - Fix forked NODE_OPTIONS except for inspect: [#28420](https://togithub.com/vercel/next.js/issues/28420) - \[ESLint] Enable caching by default: [#28349](https://togithub.com/vercel/next.js/issues/28349) - Update test config to leverage swc: [#28400](https://togithub.com/vercel/next.js/issues/28400) - Add missing `typescript` property to `NextConfig`: [#28459](https://togithub.com/vercel/next.js/issues/28459) - next/script fix duplicate scripts : [#28428](https://togithub.com/vercel/next.js/issues/28428) - Ensure error is shown correctly for empty headers field: [#28430](https://togithub.com/vercel/next.js/issues/28430) - Add default trace format that is exported automatically: [#28461](https://togithub.com/vercel/next.js/issues/28461) - Update i18n locales limit to warning: [#28429](https://togithub.com/vercel/next.js/issues/28429) - Fix handling for 204 status code with a body: [#28479](https://togithub.com/vercel/next.js/issues/28479) - Update warning when parent styles break `next/image`: [#28517](https://togithub.com/vercel/next.js/issues/28517) - Support for functional Document components: [#28515](https://togithub.com/vercel/next.js/issues/28515) - Ensure dev server side errors are correct: [#28520](https://togithub.com/vercel/next.js/issues/28520) - Add CSP to Image Optimization API: [#28620](https://togithub.com/vercel/next.js/issues/28620) ##### Documentation Changes - Fix incorrect error manifest path: [#27970](https://togithub.com/vercel/next.js/issues/27970) - Add testing docs: [#27965](https://togithub.com/vercel/next.js/issues/27965) - \[DOCS] Update testing docs: [#28064](https://togithub.com/vercel/next.js/issues/28064) - \[ESLint] Disallow inside \_document.js & inside the next/head component: [#27257](https://togithub.com/vercel/next.js/issues/27257) - Docs: Mention 3rd option 'blocking' for fallback: [#28077](https://togithub.com/vercel/next.js/issues/28077) - Add a Styling Section to next/image component docs: [#28055](https://togithub.com/vercel/next.js/issues/28055) - Improve React Strict Mode documentation.: [#28139](https://togithub.com/vercel/next.js/issues/28139) - doc: fix typo: [#28146](https://togithub.com/vercel/next.js/issues/28146) - docs: corrected the link to the example: [#28175](https://togithub.com/vercel/next.js/issues/28175) - ESLint Plugin: Prefer next script component when using the inline script for Google Analytics.: [#25147](https://togithub.com/vercel/next.js/issues/25147) - Update testing.md: [#28190](https://togithub.com/vercel/next.js/issues/28190) - docs: Add link to Cypress GitHub Actions Guide to Testing docs: [#28207](https://togithub.com/vercel/next.js/issues/28207) - Add docs for ESLint plugin settings and rule options: [#28059](https://togithub.com/vercel/next.js/issues/28059) - Add eslint rule for id attribute on inline next/script: [#27853](https://togithub.com/vercel/next.js/issues/27853) - Update supported-browsers-features.md: [#28326](https://togithub.com/vercel/next.js/issues/28326) - fix link to global stylesheet in from-create-react-app.md: [#28327](https://togithub.com/vercel/next.js/issues/28327) - docs: update font-optimization.md: [#28397](https://togithub.com/vercel/next.js/issues/28397) - Improved `next/image` docs around layouts.: [#28345](https://togithub.com/vercel/next.js/issues/28345) - Minor docs edit: cors -> CORS: [#28472](https://togithub.com/vercel/next.js/issues/28472) - Update docs for `sharp` usage to mention Vercel: [#28476](https://togithub.com/vercel/next.js/issues/28476) - Use recommended pattern in testing example: [#28404](https://togithub.com/vercel/next.js/issues/28404) - Update with-jest packages and docs: [#28209](https://togithub.com/vercel/next.js/issues/28209) - Add docs for using pageExtensions to colocate other files with page components: [#22740](https://togithub.com/vercel/next.js/issues/22740) - Small grammar fixes: [#28590](https://togithub.com/vercel/next.js/issues/28590) ##### Example Changes - Make sure all example packages has `private: true`: [#28008](https://togithub.com/vercel/next.js/issues/28008) - next-env.d.ts note in templates: [#27983](https://togithub.com/vercel/next.js/issues/27983) - Add `.gitignore` to examples that lack them: [#28003](https://togithub.com/vercel/next.js/issues/28003) - Update Firebase hosting example to use Node.js 14.: [#27988](https://togithub.com/vercel/next.js/issues/27988) - Examples: Jotai: [#27940](https://togithub.com/vercel/next.js/issues/27940) - Remove `licence` from all `example/package.json` that has them: [#28007](https://togithub.com/vercel/next.js/issues/28007) - Add ci script to check examples: [#28009](https://togithub.com/vercel/next.js/issues/28009) - Replace CSS tag with JS import: [#28143](https://togithub.com/vercel/next.js/issues/28143) - Fixed typos that existed on some files: [#28314](https://togithub.com/vercel/next.js/issues/28314) - Add Temporal example: [#28348](https://togithub.com/vercel/next.js/issues/28348) - \[examples] Added `with-couchbase` example: [#27184](https://togithub.com/vercel/next.js/issues/27184) - \[examples] Add ElasticSearch example: [#28043](https://togithub.com/vercel/next.js/issues/28043) - Fix: changing import syntax slightly to ensure success with `create-next-app`: [#28431](https://togithub.com/vercel/next.js/issues/28431) - Add prop-types in package.json: [#28481](https://togithub.com/vercel/next.js/issues/28481) - Update to use the latest MongoDB best practices to limit connection pooling issues.: [#28350](https://togithub.com/vercel/next.js/issues/28350) - Add apiVersion to config: [#28610](https://togithub.com/vercel/next.js/issues/28610) ##### Misc Changes - Tests: Execute development-logs tests.: [#27996](https://togithub.com/vercel/next.js/issues/27996) - Fix publish native script: [#28037](https://togithub.com/vercel/next.js/issues/28037) - Authenticate npm before publishing native packages: [#28041](https://togithub.com/vercel/next.js/issues/28041) - publish flow fixes: [#28050](https://togithub.com/vercel/next.js/issues/28050) - USe await correctly: [#28053](https://togithub.com/vercel/next.js/issues/28053) - Refactor development-logs removing duplicated code.: [#28049](https://togithub.com/vercel/next.js/issues/28049) - Fix gh action workflow when docs changed: [#28092](https://togithub.com/vercel/next.js/issues/28092) - Skip native ci steps for docs only changes: [#28101](https://togithub.com/vercel/next.js/issues/28101) - Add setup for m1 build: [#28138](https://togithub.com/vercel/next.js/issues/28138) - fix(tests): fixes typo in basic integration test: [#28158](https://togithub.com/vercel/next.js/issues/28158) - Fix crash of lint rule no-document-import-in-page: [#28148](https://togithub.com/vercel/next.js/issues/28148) - docs: make contributing.md more contributor-friendly: [#27913](https://togithub.com/vercel/next.js/issues/27913) - Update polling env var for tests in CI: [#28264](https://togithub.com/vercel/next.js/issues/28264) - Ensure all packages are packed while tracing: [#28263](https://togithub.com/vercel/next.js/issues/28263) - Use temp repo copy while linking packages: [#28301](https://togithub.com/vercel/next.js/issues/28301) - feat: upgrade swc/core to 1.2.80: [#28347](https://togithub.com/vercel/next.js/issues/28347) - Move unit tests to one folder and migrate them to TypeScript: [#28427](https://togithub.com/vercel/next.js/issues/28427) - Tests: Adds test to data-nimg data attribute based on layout prop.: [#28444](https://togithub.com/vercel/next.js/issues/28444) - Remove unused imports - \[ESLint Plugin] Handles edge case for `no-import-document-in-page` rule: [#28261](https://togithub.com/vercel/next.js/issues/28261) - Tests: Remove unnecessary await: [#28594](https://togithub.com/vercel/next.js/issues/28594) ##### Credits Huge thanks to [@delbaoliveira](https://togithub.com/delbaoliveira), [@padmaia](https://togithub.com/padmaia), [@andersonleite](https://togithub.com/andersonleite), [@stefanprobst](https://togithub.com/stefanprobst), [@oBusk](https://togithub.com/oBusk), [@sokra](https://togithub.com/sokra), [@xnuk](https://togithub.com/xnuk), [@styfle](https://togithub.com/styfle), [@leerob](https://togithub.com/leerob), [@devknoll](https://togithub.com/devknoll), [@huozhi](https://togithub.com/huozhi), [@timneutkens](https://togithub.com/timneutkens), [@awareness481](https://togithub.com/awareness481), [@agektmr](https://togithub.com/agektmr), [@gu-stav](https://togithub.com/gu-stav), [@sampoder](https://togithub.com/sampoder), [@Thisen](https://togithub.com/Thisen), [@ijjk](https://togithub.com/ijjk), [@oscarafuentes](https://togithub.com/oscarafuentes), [@AryanBeezadhur](https://togithub.com/AryanBeezadhur), [@bmuenzenmeyer](https://togithub.com/bmuenzenmeyer), [@tdkn](https://togithub.com/tdkn), [@rgabs](https://togithub.com/rgabs), [@urko-pineda](https://togithub.com/urko-pineda), [@davecaruso](https://togithub.com/davecaruso), [@kevinold](https://togithub.com/kevinold), [@ctjlewis](https://togithub.com/ctjlewis), [@chrislloyd](https://togithub.com/chrislloyd), [@mrmckeb](https://togithub.com/mrmckeb), [@housseindjirdeh](https://togithub.com/housseindjirdeh), [@hiro0218](https://togithub.com/hiro0218), [@Bezmehrabi](https://togithub.com/Bezmehrabi), [@atcastle](https://togithub.com/atcastle), [@janicklas-ralph](https://togithub.com/janicklas-ralph), [@lorensr](https://togithub.com/lorensr), [@lekterable](https://togithub.com/lekterable), [@vcnc-hex](https://togithub.com/vcnc-hex), [@ejscribner](https://togithub.com/ejscribner), [@Andarist](https://togithub.com/Andarist), [@aravindputrevu](https://togithub.com/aravindputrevu), [@robbieaverill](https://togithub.com/robbieaverill), [@zhafri-shafiq](https://togithub.com/zhafri-shafiq), [@htunnicliff](https://togithub.com/htunnicliff), [@kukicado](https://togithub.com/kukicado), [@OzzieOrca](https://togithub.com/OzzieOrca), [@mikehedman](https://togithub.com/mikehedman), and [@kmelve](https://togithub.com/kmelve) for helping! ### [`v11.1.0`](https://togithub.com/vercel/next.js/releases/tag/v11.1.0) [Compare Source](https://togithub.com/vercel/next.js/compare/v11.0.1...v11.1.0) A security team from one of our partners noticed an issue in Next.js that allowed for an open redirect to occur. Specially encoded paths could be used when `pages/_error.js` was statically generated allowing an open redirect to occur to an external site. In general, this redirect does not directly harm users although can allow for phishing attacks by redirecting to an attacker's domain from a trusted domain. We recommend upgrading to the latest version of Next.js to improve the overall security of your application. #### How to Upgrade - We have released patch versions for both the stable and canary channels of Next.js. - To upgrade run `npm install next@latest --save` #### Impact - **Affected:** Users of Next.js between 10.0.5 and 10.2.0 - **Affected:** Users of Next.js between 11.0.0 and 11.0.1 using `pages/_error.js` without `getInitialProps` - **Affected:** Users of Next.js between 11.0.0 and 11.0.1 using `pages/_error.js` and `next export` - **Not affected**: Deployments on Vercel ([vercel.com](https://vercel.com)) are not affected - **Not affected:** Deployments **with** `pages/404.js` We recommend everyone to upgrade regardless of whether you can reproduce the issue or not. ##### How to Assess Impact If you think sensitive code or data could have been exposed, you can filter logs of affected sites by `//` (double slash at the start of the url) followed by a domain. #### What is Being Done As Next.js has grown in popularity and usage by enterprises, it has received the attention of security researchers and auditors. We are thankful to Gabriel Benmergui from Robinhood for their investigation and discovery of the original bug and subsequent responsible disclosure. We've landed a patch that ensures path parsing is handled properly for these paths so that the open redirect can no longer occur. Regression tests for this attack were added to the [security](https://togithub.com/zeit/next.js/blob/canary/test/integration/production/test/security.js) integration test suite - We have notified known Next.js users in advance of this publication. - A public CVE was released. - We encourage responsible disclosure of future reports. Please email us at `security@vercel.com`. We are actively monitoring this mailbox. *** #### Release notes ##### Core Changes - Don't test image domains in test env: [#26502](https://togithub.com/vercel/next.js/issues/26502) - Fix props not updating when changing the locale and keeping hash: [#26205](https://togithub.com/vercel/next.js/issues/26205) - Allow user to override next-image-loader: [#26548](https://togithub.com/vercel/next.js/issues/26548) - Add logging when a custom babelrc is loaded: [#26570](https://togithub.com/vercel/next.js/issues/26570) - Add comment to not edit in next-env file: [#26573](https://togithub.com/vercel/next.js/issues/26573) - Add trace url on bootup: [#26594](https://togithub.com/vercel/next.js/issues/26594) - Add check for ObjectExpression when iterating on tags for font optimization: [#26608](https://togithub.com/vercel/next.js/issues/26608) - Fix GSP redirect cache error: [#26627](https://togithub.com/vercel/next.js/issues/26627) - Correct statusCode when visiting \_error directly: [#26610](https://togithub.com/vercel/next.js/issues/26610) - fix: next dynamic with jest: [#26614](https://togithub.com/vercel/next.js/issues/26614) - Ensure API routes are not available under the locale: [#26629](https://togithub.com/vercel/next.js/issues/26629) - Fix image content type octet stream 400: [#26705](https://togithub.com/vercel/next.js/issues/26705) - \[ESLint] Adds --max-warnings flag to `next lint`: [#26697](https://togithub.com/vercel/next.js/issues/26697) - Simplify `next-dev-server` implementation: [#26230](https://togithub.com/vercel/next.js/issues/26230) - Move code shared between server/client to "shared" folder: [#26734](https://togithub.com/vercel/next.js/issues/26734) - Move next-server directory files to server directory: [#26756](https://togithub.com/vercel/next.js/issues/26756) - Support new hydrate API in latest react 18 alpha release: [#26664](https://togithub.com/vercel/next.js/issues/26664) - Add upstream `max-age` to optimized image: [#26739](https://togithub.com/vercel/next.js/issues/26739) - Fix blurred image position when using objectPosition: [#26590](https://togithub.com/vercel/next.js/issues/26590) - Leverage blocked page for \_error: [#26748](https://togithub.com/vercel/next.js/issues/26748) - fix: detect loop in client error page: [#26567](https://togithub.com/vercel/next.js/issues/26567) - Add `onLoadingComplete()` prop to Image component: [#26824](https://togithub.com/vercel/next.js/issues/26824) - Add "Vary: Accept" header to /\_next/image responses: [#26788](https://togithub.com/vercel/next.js/issues/26788) - Add additional tests for image type detection: [#26832](https://togithub.com/vercel/next.js/issues/26832) - Fix immutable header for image with static import & unoptimized: [#26836](https://togithub.com/vercel/next.js/issues/26836) - Make sure 404 pages do not get cached by a CDN when using next start: [#24983](https://togithub.com/vercel/next.js/issues/24983) - Don't emit duplicate image files: [#26843](https://togithub.com/vercel/next.js/issues/26843) - Warn when response body is larger than 5mb: [#26831](https://togithub.com/vercel/next.js/issues/26831) - Fix: added the key property to the pre next scripts: [#26646](https://togithub.com/vercel/next.js/issues/26646) - Ensure API route errors are propagated in minimal mode: [#26875](https://togithub.com/vercel/next.js/issues/26875) - 5MB -> 4MB body size limit: [#26887](https://togithub.com/vercel/next.js/issues/26887) - \[ESLint] Update default `.eslintrc` file created to have `.json` format: [#26884](https://togithub.com/vercel/next.js/issues/26884) - Refactor decode failures: [#26899](https://togithub.com/vercel/next.js/issues/26899) - Add initial `ResponsePayload` support: [#26938](https://togithub.com/vercel/next.js/issues/26938) - Fix typo in route-loader: [#26942](https://togithub.com/vercel/next.js/issues/26942) - More explicit typing for `IncrementalCache` API: [#26941](https://togithub.com/vercel/next.js/issues/26941) - Fix merge issue and use `respondWith`: [#26961](https://togithub.com/vercel/next.js/issues/26961) - (next/image): Merge query string params in imgix loader: [#26719](https://togithub.com/vercel/next.js/issues/26719) - Fix: (rewrites) incorrect parsing of destination query: [#26619](https://togithub.com/vercel/next.js/issues/26619) - Fix forward slash encoding while interpolating: [#26963](https://togithub.com/vercel/next.js/issues/26963) - update webpack to 5.43.0: [#26979](https://togithub.com/vercel/next.js/issues/26979) - Rename `next/script` interface Props to ScriptProps: [#26990](https://togithub.com/vercel/next.js/issues/26990) - Don't lazy-load already-loaded image in client-side transition: [#26968](https://togithub.com/vercel/next.js/issues/26968) - Loosen `next/image` TS types for `width` and `height`: [#26991](https://togithub.com/vercel/next.js/issues/26991) - Add `dangerously-unoptimized` loader for next/image: [#26847](https://togithub.com/vercel/next.js/issues/26847) - Fix hash change events not firing with i18n: [#26994](https://togithub.com/vercel/next.js/issues/26994) - Loosen `next/image` TS types for `src`: [#26996](https://togithub.com/vercel/next.js/issues/26996) - Provide Next.js postcss version to cssnano-simple: [#26952](https://togithub.com/vercel/next.js/issues/26952) - Rename next/image `dangerously-unoptimized` to `custom` and warn when applicable: [#26998](https://togithub.com/vercel/next.js/issues/26998) - Add newline to the end of `next-env.d.ts`: [#27028](https://togithub.com/vercel/next.js/issues/27028) - Add performance tracing for next-image-loader: [#27043](https://togithub.com/vercel/next.js/issues/27043) - Include message body in redirect responses: [#25257](https://togithub.com/vercel/next.js/issues/25257) - add support for esm externals: [#27069](https://togithub.com/vercel/next.js/issues/27069) - Enhance `next dev` performance with placeholder=blur: [#27061](https://togithub.com/vercel/next.js/issues/27061) - Add batching to zipkin reporter: [#27082](https://togithub.com/vercel/next.js/issues/27082) - Bind sendBeacon to navigator: [#26601](https://togithub.com/vercel/next.js/issues/26601) - Fall back to fallbackSend when send is false: [#27113](https://togithub.com/vercel/next.js/issues/27113) - Upgrades `web-vitals` to v1.1.2.: [#25272](https://togithub.com/vercel/next.js/issues/25272) - Prevent timeout when loading routes in development: [#25749](https://togithub.com/vercel/next.js/issues/25749) - Workaround for Node.js 16+ on Apple Silicon M1: [#27031](https://togithub.com/vercel/next.js/issues/27031) - Replace `withCoalescedInvoke` with `ResponseCache`: [#26997](https://togithub.com/vercel/next.js/issues/26997) - Add some missing fields to the NextConfig type: [#27126](https://togithub.com/vercel/next.js/issues/27126) - Update redirect regexes to not match \_next: [#27143](https://togithub.com/vercel/next.js/issues/27143) - Bump babel target to Node.js 12: [#27147](https://togithub.com/vercel/next.js/issues/27147) - Use SWC to compile Next.js core server files: [#27167](https://togithub.com/vercel/next.js/issues/27167) - Fix css minify incorrectly duplicating variables: [#27150](https://togithub.com/vercel/next.js/issues/27150) - Fix gsp generation with file extension: [#27144](https://togithub.com/vercel/next.js/issues/27144) - Add `minimumCacheTTL` config for Image Optimization: [#27200](https://togithub.com/vercel/next.js/issues/27200) - Fix Script beforeInteractive on navigation: [#26995](https://togithub.com/vercel/next.js/issues/26995) - improve static generation UX: [#27171](https://togithub.com/vercel/next.js/issues/27171) - Add warning for large number of routes: [#27214](https://togithub.com/vercel/next.js/issues/27214) - Add x-forward headers to external rewrites: [#17557](https://togithub.com/vercel/next.js/issues/17557) - \[ESLint] Remove error when file patterns are unmatched + ESLint setup changes: [#27119](https://togithub.com/vercel/next.js/issues/27119) - Fix inline scripts being duplicated when used with `next/script` component: [#27218](https://togithub.com/vercel/next.js/issues/27218) - Fix `minimumCacheTTL` so it doesn't affect browser caching: [#27307](https://togithub.com/vercel/next.js/issues/27307) - Fix default server host value causing issues on Windows: [#27306](https://togithub.com/vercel/next.js/issues/27306) - Fix `placeholder=blur` inside `Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.