chore(deps): bump the npm_and_yarn group across 3 directories with 2 updates

[dependabot]

Bumps the npm_and_yarn group with 1 update in the /e2e directory: tar.
Bumps the npm_and_yarn group with 1 update in the /packages/devnext directory: next.
Bumps the npm_and_yarn group with 1 update in the /packages/playground-next directory: next.

Updates tar from 6.1.15 to 6.2.1

Changelog

Sourced from tar's changelog.

Changelog

7.5

• Added zstd compression support.

7.4

• Deprecate onentry in favor of onReadEntry for clarity.

7.3

• Add onWriteEntry option

7.2

• DRY the command definitions into a single makeCommand method, and update the type signatures to more appropriately infer the return type from the options and arguments provided.

7.1

• Update minipass to v7.1.0
• Update the type definitions of write() and end() methods on Unpack and Parser classes to be compatible with the NodeJS.WritableStream type in the latest versions of @types/node.

7.0

• Drop support for node <18
• Rewrite in TypeScript, provide ESM and CommonJS hybrid interface
• Add tree-shake friendly exports, like import('tar/create') and import('tar/read-entry') to get individual functions or classes.
• Add chmod option that defaults to false, and deprecate noChmod. That is, reverse the default option regarding explicitly setting file system modes to match tar entry settings.
• Add processUmask option to avoid having to call process.umask() when chmod: true (or noChmod: false) is set.

6.2

• Add support for brotli compression
• Add maxDepth option to prevent extraction into excessively deep folders.

... (truncated)

Commits

• bef7b1e 6.2.1
• fe8cd57 prevent extraction in excessively deep subfolders
• fe7ebfd remove security.md
• 5bc9d40 6.2.0
• fe1ef5e changelog 6.2
• e483220 get rid of npm lint stuff
• 689928a ci that works outside of npm org
• db6f539 file inference improvements for .tbr and .tgz
• 336fa8f refactor: dry and other pr comments
• eeba222 chore: lint fixes
• Additional commits viewable in compare view

Updates next from 13.2.4 to 14.2.32

Commits

• 89ee561 v14.2.32
• 6a974ad [backport v14]: fix router handling when setting a location response header (...
• 55f7662 v14.2.31
• 5dd68a5 [backport v14]: fix(next/image): improve and simplify detect-content-type (#8...
• bcc7c65 [backport v14]: fix(next/image): fix image-optimizer.ts headers (#82114) (#82...
• 243072b v14.2.30
• f523d4a [backport]: config.allowedDevOrigins (#80410)
• ca92115 v14.2.29
• ec9ee87 Only share incremental cache for edge in next start (#79389)
• e65628a v14.2.28
• Additional commits viewable in compare view

Updates next from 15.1.4 to 15.4.7

Commits

• 89ee561 v14.2.32
• 6a974ad [backport v14]: fix router handling when setting a location response header (...
• 55f7662 v14.2.31
• 5dd68a5 [backport v14]: fix(next/image): improve and simplify detect-content-type (#8...
• bcc7c65 [backport v14]: fix(next/image): fix image-optimizer.ts headers (#82114) (#82...
• 243072b v14.2.30
• f523d4a [backport]: config.allowedDevOrigins (#80410)
• ca92115 v14.2.29
• ec9ee87 Only share incremental cache for edge in next start (#79389)
• e65628a v14.2.28
• Additional commits viewable in compare view

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will 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 version will 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
  You can disable automated security fix PRs for this repo from the Security Alerts page.

---

Note

Updates tar and Next.js versions across e2e, devnext, and playground-next packages.

• Dependencies:
  • e2e/yarn.lock: update tar from 6.1.15 to 6.2.1.
  • packages/devnext/package.json: bump next from 13.2.4 to 14.2.32.
  • packages/playground-next/package.json: bump next from 15.1.4 to 15.4.7.

^{Written by Cursor Bugbot for commit ad93344. This will update automatically on new commits. Configure here.}

[cursor]

Bug: ESLint Config Mismatch Breaks Next.js Linting

Updating next to 14.2.32 while leaving eslint-config-next at 13.2.4 creates a major version mismatch. The eslint-config-next package should match the major version of next to ensure ESLint rules are compatible with the Next.js version being used, otherwise linting may fail or produce incorrect results.

 

[cursor]

Bug: Next.js ESLint Mismatch Causes Linting Failures

Updating next to 15.4.7 while leaving eslint-config-next at 15.1.4 creates a version mismatch. The eslint-config-next package should be updated alongside next to ensure ESLint rules remain compatible with the Next.js version being used, otherwise linting may produce incorrect results or fail.