Skip to content

Commit

Permalink
chore(npm): bump the next-eslint-dependencies group
Browse files Browse the repository at this point in the history
Bumps the next-eslint-dependencies group in /Website with 2 updates: [eslint-config-next](https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next) and [next](https://github.com/vercel/next.js).


Updates `eslint-config-next` from 15.1.1 to 15.1.2
- [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/v15.1.2/packages/eslint-config-next)

Updates `next` from 15.1.1 to 15.1.2
- [Release notes](https://github.com/vercel/next.js/releases)
- [Changelog](https://github.com/vercel/next.js/blob/canary/release.js)
- [Commits](vercel/next.js@v15.1.1...v15.1.2)

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

Signed-off-by: dependabot[bot] <support@github.com>
  • Loading branch information
dependabot[bot] authored Dec 20, 2024
1 parent c19d123 commit 1906eb6
Show file tree
Hide file tree
Showing 2 changed files with 50 additions and 50 deletions.
96 changes: 48 additions & 48 deletions Website/package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

4 changes: 2 additions & 2 deletions Website/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -12,8 +12,8 @@
"@headlessui/react": "^2.2.0",
"autoprefixer": "10.4.20",
"eslint": "8.57.0",
"eslint-config-next": "15.1.1",
"next": "15.1.1",
"eslint-config-next": "15.1.2",
"next": "15.1.2",
"postcss": "8.4.49",
"react": "19.0.0",
"react-dom": "19.0.0",
Expand Down

0 comments on commit 1906eb6

Please sign in to comment.