chore(deps): bump the nextjs group with 3 updates #6234
Conversation
dependabot
bot
added
dependencies
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/nextjs-7d55e55f71
branch
6 times, most recently
from
a06c324 to
6fe8c6f
Compare
Bumps the nextjs group with 3 updates: [@next/third-parties](https://github.com/vercel/next.js/tree/HEAD/packages/third-parties), [next](https://github.com/vercel/next.js) and [eslint-config-next](https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next). Updates `@next/third-parties` from 15.5.4 to 16.0.0 - [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/v16.0.0/packages/third-parties) Updates `next` from 15.5.4 to 16.0.0 - [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.5.4...v16.0.0) Updates `eslint-config-next` from 15.5.4 to 16.0.0 - [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/v16.0.0/packages/eslint-config-next) --- updated-dependencies: - dependency-name: "@next/third-parties" dependency-version: 16.0.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: nextjs - dependency-name: next dependency-version: 16.0.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: nextjs - dependency-name: eslint-config-next dependency-version: 16.0.0 dependency-type: direct:development update-type: version-update:semver-major dependency-group: nextjs ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/nextjs-7d55e55f71
branch
from
6fe8c6f to
7cf2ee4
Compare
Bumps the nextjs group with 3 updates: [@next/third-parties](https://github.com/vercel/next.js/tree/HEAD/packages/third-parties), [next](https://github.com/vercel/next.js) and [eslint-config-next](https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next). Updates `@next/third-parties` from 15.5.4 to 16.0.0 - [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/v16.0.0/packages/third-parties) Updates `next` from 15.5.4 to 16.0.0 - [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.5.4...v16.0.0) Updates `eslint-config-next` from 15.5.4 to 16.0.0 - [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/v16.0.0/packages/eslint-config-next) --- updated-dependencies: - dependency-name: "@next/third-parties" dependency-version: 16.0.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: nextjs - dependency-name: next dependency-version: 16.0.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: nextjs - dependency-name: eslint-config-next dependency-version: 16.0.0 dependency-type: direct:development update-type: version-update:semver-major dependency-group: nextjs ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/nextjs-7d55e55f71
branch
from
7cf2ee4 to
e8d4473
Compare
…ithub.com/mozilla/blurts-server into dependabot/npm_and_yarn/nextjs-7d55e55f71
TODO: Address new eslint errors
|
Blocked by mozilla/glean.js#2030, or requires type shims |
@kschelonka do you know if a release was done containing your changes as referenced in mozilla/glean.js#2030 (comment) ? I think it'd be good to get this week's release out before landing this, so we have some time to test on stage. If there are any other known blockers to landing this please let me know. |
I requested a release. Looking at their release history, looks like one was done yesterday with my changes: https://github.com/mozilla/glean.js/releases/tag/v5.0.7 |
|
@dependabot rebase |
|
Looks like this PR has been edited by someone other than Dependabot. That means Dependabot can't rebase it - sorry! If you're happy for Dependabot to recreate it from scratch, overwriting any edits, you can request |
…rn/nextjs-7d55e55f71
…on: bundler can resolve the side-effect import used across the project
|
Like #6300 (comment), if we're changing |
Bumps the nextjs group with 3 updates: @next/third-parties, next and eslint-config-next.
Updates
@next/third-partiesfrom 15.5.4 to 16.0.0Release notes
Sourced from
@next/third-parties's releases.... (truncated)
Commits
950609fv16.0.0fcc3157v16.0.0-canary.19c0b086cv16.0.0-canary.18446cf30v16.0.0-canary.1776a9a1dv16.0.0-canary.16ad9013ev16.0.0-canary.15a83f3c0v16.0.0-canary.14b38921dv16.0.0-canary.1314018a9v16.0.0-canary.12fa70898v16.0.0-canary.11Updates
nextfrom 15.5.4 to 16.0.0Release notes
Sourced from next's releases.
... (truncated)
Commits
950609fv16.0.0fcc3157v16.0.0-canary.19c0b086cv16.0.0-canary.18f770793logger: skip logging full element (#85194)074262bOnly allow node runtime in proxy (#85139)47ceda3[cache components] persist cache bypass UI until it's disabled (#85190)b66c1d6Remove layout-router sticky/fixed debug warning (#85193)96754b6Tweaks to blocking route error message (#85191)48bb490docs: upgrade from 15 to 16 (#85176)9b34b65[upgrade] Version gate adding--turbopackflag (#85180)Updates
eslint-config-nextfrom 15.5.4 to 16.0.0Release notes
Sourced from eslint-config-next's releases.
... (truncated)
Commits
950609fv16.0.0fcc3157v16.0.0-canary.19c0b086cv16.0.0-canary.18446cf30v16.0.0-canary.1776a9a1dv16.0.0-canary.16ad9013ev16.0.0-canary.15a83f3c0v16.0.0-canary.14b38921dv16.0.0-canary.1314018a9v16.0.0-canary.12fa70898v16.0.0-canary.11Dependabot 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 mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions