Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump next from 11.1.0 to 11.1.1 in /examples/next-js-example #1

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Sep 1, 2021

Bumps next from 11.1.0 to 11.1.1.

Release notes

Sourced from next's releases.

v11.1.1

Core Changes

  • Next.js swc publish flow: #27984
  • Ensure config file message is only shown once: #28017
  • Add missing fields to NextConfig type: #27974
  • use a shared worker pool for collecting page data and static page generation: #27924
  • Use @​next scope for native packages: #28046
  • Fix generateBuildId type that can be async function: #28040
  • Fix image optimization encoding url: #28045
  • Clean up Document in preparation for streaming: #28032
  • Render as a concatenation of streams: #28082
  • Add support for dynamic HTML: #28085
  • Support suspense in next dynamic: #27611
  • Handle blob urls in image component: #27975
  • Bypass webpack compilation for precompiled @​next/polyfills-nomodule: #27596
  • Update util to 0.12.4: #27939
  • Remove duplicate doctypes: #28089
  • Fix revalidate for initial notFound: true paths: #28097
  • Add proper error when failing to load next.config.js: #28099
  • Fix: wrong link error message: #28127
  • Add support for Jaeger trace target: #28129
  • Enable pure client suspense in blocking rendering: #28165
  • Add entrypoint tracing: #25538
  • Add module type to build-module trace: #28128
  • Update to latest babel versions: #28174
  • Improve jaeger traces: #28168
  • fix development mode bug with pages with "+" and other special characters: #28122
  • let loaders automatically infer source map setting: #28204
  • Avoid fs write next-env.d.ts on read-only filesystems: #28206
  • Document usage of suspense option of next/dynamic: #28210
  • Add warning when parent styles break next/image: #28221
  • Use zen-observable library: #28214
  • Fix HMR when custom _app or _document is removed: #28227
  • Add relationship between issuer and module to traces: #28192
  • Update generating next-server dependencies: #28223
  • Fix next/image blur placeholder when JS is disabled: #28269
  • Ensure adding _app/_document HMRs correctly: #28279
  • upgrade webpack to 5.51.1: #28291
  • [ESLint] Adds process.exit to next lint success output: #28299
  • Fix next env vars injection in dynamic: #28309
  • Add layout to data-nimg attribute: #28312
  • Add data attribute to script component: #28310
  • Ensure @​babel/core is de-duped when nccing: #28384
  • Fix forked NODE_OPTIONS except for inspect: #28420
  • [ESLint] Enable caching by default: #28349
  • Update test config to leverage swc: #28400
  • Add missing typescript property to NextConfig: #28459
  • next/script fix duplicate scripts : #28428
  • Ensure error is shown correctly for empty headers field: #28430

... (truncated)

Commits

Dependabot compatibility score

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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

Bumps [next](https://github.com/vercel/next.js) from 11.1.0 to 11.1.1.
- [Release notes](https://github.com/vercel/next.js/releases)
- [Changelog](https://github.com/vercel/next.js/blob/canary/release.js)
- [Commits](vercel/next.js@v11.1.0...v11.1.1)

---
updated-dependencies:
- dependency-name: next
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Sep 1, 2021
@dependabot @github
Copy link
Author

dependabot bot commented on behalf of github Dec 9, 2021

Superseded by #3.

@dependabot dependabot bot closed this Dec 9, 2021
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/examples/next-js-example/next-11.1.1 branch December 9, 2021 05:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants