fix(deps): update dependency @next/eslint-plugin-next to v15.4.0-canary.108

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@next/eslint-plugin-next (source)	15.4.0-canary.104 -> 15.4.0-canary.108

---

Release Notes

vercel/next.js (@​next/eslint-plugin-next)

v15.4.0-canary.108

Compare Source

Core Changes

• [segment explorer] reset error and not-found boundary: #​81115
• [devtool] enable segment explorer when new panel present by default: #​81152

Example Changes

• chore: fix typos in rust files: #​81113

Misc Changes

• Update nextjs-bot config: #​81138
• [turbopack] Remove some unnecessary awaits now that FileSystemPath is synchronously available.: #​81090
• Run front-sync after deployment tests finish : #​81023
• Docs: moved table for Unsupported Metadata to the correct location: #​80979
• fix(next-swc): Apply SWC minifier bugfixes: #​81098
• Update Rspack development test manifest: #​81103
• Update Rspack production test manifest: #​81102
• Update Turbopack production test manifest: #​81105
• Update Turbopack development test manifest: #​81104
• Add more test cases to the dynamicIO sync IO access test suite: #​81045
• chore(turbo-tasks-backend): Remove unused support for nested database operations: #​80816
• Turbopack: simplify ReducedGraphs and find_server_entries: #​81118
• [turbopack] Remove an unnecessary clone: #​81153
• [turbopack] Move static type ID variables into getters: #​81150
• refactor(turbo-tasks-backend): Remove ExecuteContextImpl::lower_read_transaction: #​80822

Credits

Huge thanks to @​ijjk, @​lukesandberg, @​padmaia, @​aacosta11, @​xusd320, @​kdy1, @​huozhi, @​vercel-release-bot, @​unstubbable, @​bgw, and @​mischnic for helping!

v15.4.0-canary.107

Compare Source

Core Changes

• Revert "[devtool] merge segment explorer flag into panel ui flag (#​81085)": #​81131

Misc Changes

• Fix flakey devtools test: #​81127
• [turbopack] Defend against json cyles in our execution tests: #​81079
• [turbopack] Implement Issue::source on more Issue subtypes: #​80874
• Update workflows for nextjs-bot: #​81134

Credits

Huge thanks to @​mischnic, @​lukesandberg, @​ijjk, and @​huozhi for helping!

v15.4.0-canary.106

Compare Source

Misc Changes

• Fix flakey devtools test: #​81127
• [turbopack] Defend against json cyles in our execution tests: #​81079
• [turbopack] Implement Issue::source on more Issue subtypes: #​80874

Credits

Huge thanks to @​mischnic and @​lukesandberg for helping!

v15.4.0-canary.105

Compare Source

Core Changes

• Update font data: #​81093
• Upgrade React from 4db4b21c-20250626 to 65c4decb-20250630: #​81077
• [node-webstreams] Remove unused App externals from next-server bundler config: #​81039
• Turbopack: apply browserslist config in dev: #​81075
• [build] remove the default imports for error boundary: #​81000
• Turbopack: also inline env vars with undefined value: #​80990
• [devtools]: default to issues tab when error overlay is programmatically toggled: #​81091
• [devtool] merge segment explorer flag into panel ui flag: #​81085

Misc Changes

• [turbopack] Make internal functions private and use rcstr! macro: #​81041
• build(turbopack): Update swc_core to v29.4.0: #​81092
• Turbopack: Improve compaction in Persistent Caching: #​80860
• Turbopack: guard against more eventual consistency: #​81080
• Turbopack: instrument scope hoisting with tracing spans: #​81078
• [node-webstreams] Remove unused PagesApi matching condition when setting react-server: #​81037
• docs: fix grammatical error in upgrading to v15 guide: #​81038
• perf(turbopack): Disable concurrent of the SWC minifier.: #​80981
• Revert "perf(turbopack/rcstr): Add serialization-time optimization (#​78645)": #​81112
• Docs: paper cuts July 1st : #​81109
• Turbopack: scope hoist tree shaking modules as well: #​80527

Credits

Huge thanks to @​lukesandberg, @​kdy1, @​sokra, @​mischnic, @​eps1lon, @​extoci, @​huozhi, @​icyJoseph, and @​ztanner for helping!

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[changeset-bot]

🦋 Changeset detected

Latest commit: 17da989

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages

Name	Type
@tcd-devkit/eslint-config-next	Patch
@tcd-devkit/eslint-preset-next	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Join our Discord community for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.