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 eslint-config-next from 13.0.0 to 13.0.1 #1178

Merged

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Nov 1, 2022

Bumps eslint-config-next from 13.0.0 to 13.0.1.

Release notes

Sourced from eslint-config-next's releases.

v13.0.1

Core Changes

  • Rest of options in experimental.turbotrace and documentation: #41817
  • Fix revalidate check in client component: #41917
  • Add data attribute to div to distinguish it: #41889
  • Fix lint cli help: #41783
  • [Doc] Update inline documentation for next/link: #41871
  • feat(edge): split NextCookies to RequestCookies and ResponseCookies: #41526
  • Show error message when using legacy props on new next/image: #41930
  • Upgrade Edge Runtime: #41987
  • Revert "Include frameworks in main-app": #41997
  • fix(next/dev): do not suppress error from bindings: #41989
  • Fix page static info extractor for app dir: #42001
  • Add never return type for redirect() and notFound(): #42009
  • Google fonts multiple weights & styles: #42008
  • Merge app internal chunk into main chunk for layouts: #41902
  • Fix build type error of page params: #42019
  • Allow disabling Strict mode in app: #41894
  • Update react next channel: #42021
  • Fix turbo custom config detection: #42022
  • Fix css modules imports in client components: #42077
  • fix: Data URL images with 'fill' are always triggering 'missing sizes' warning: #42030
  • types: leverage webpack types and remove casting: #42104
  • Fix CSS imports from outside of the app dir when src folder is present: #42108
  • Remove react root condition and always use concurrent mode: #42141
  • Keep react-dom/server.node in precompiled: #42138
  • Warn when legacy prop detected on next/image: #42102
  • Fix failing codemod test url-to-withrouter: #42109
  • Improve TypeScript plugin error when the configuration is not statically analyzable: #42062
  • Ensure app revalidate has correct default: #42168
  • Update turbo crates: #42014
  • Update vscode config handling: #42169
  • fix: allow resolving large JSON data in server components: #42025
  • issue-41925 fix: skip duplicate props when transferring props from anchor to link: #42158
  • Ensure we detect config correctly with turbo flag: #42201
  • update turbo version: #42228
  • Fix CSS modules imports from outside of the root directory: #42106
  • Default font config fix: #42235
  • Multiple local font weights and styles: #42232
  • Optimize bundle size for appDir: #42252
  • Add event for dev process stop: #42255
  • Add E2E test for @​vercel/og API route: #42258

Documentation Changes

  • [Doc] Update Next.js + Static Web Apps: #41857
  • Update the documentation.: #41758
  • Fix invalid markdown lang: #41926
  • Fix more incorrect markdown langs: #41939

... (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)

Bumps [eslint-config-next](https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next) from 13.0.0 to 13.0.1.
- [Release notes](https://github.com/vercel/next.js/releases)
- [Changelog](https://github.com/vercel/next.js/blob/canary/release.js)
- [Commits](https://github.com/vercel/next.js/commits/v13.0.1/packages/eslint-config-next)

---
updated-dependencies:
- dependency-name: eslint-config-next
  dependency-type: direct:development
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Nov 1, 2022
@vercel
Copy link

vercel bot commented Nov 1, 2022

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated
gitmoji ✅ Ready (Inspect) Visit Preview Nov 1, 2022 at 9:20AM (UTC)

@carloscuesta carloscuesta removed the javascript Pull requests that update Javascript code label Nov 1, 2022
@carloscuesta carloscuesta merged commit e57e5e1 into master Nov 1, 2022
@carloscuesta carloscuesta deleted the dependabot/npm_and_yarn/eslint-config-next-13.0.1 branch November 1, 2022 09:50
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 3, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant