Revert "Bump eslint-config-next from 15.5.0 to 15.5.2 in /landing-page"

[JaclynCodes]

Reverts #306

[coderabbitai]

📝 Walkthrough

Summary by CodeRabbit

• Chores
  • Updated development tooling configuration; no user-facing changes or functionality impacted.

Walkthrough

Downgraded the devDependency eslint-config-next from version 15.5.2 to 15.5.0 in landing-page/package.json. No other files or exports were changed.

Changes

Cohort / File(s)	Summary
Dependency Version Update landing-page/package.json	Downgrade eslint-config-next in devDependencies from 15.5.2 to 15.5.0

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I thump my paws and nod, “Just so,”
A tiny hop from two to oh.
Linting winds now slightly turn,
Version pins that rabbits learn.
Carrot-quiet, deps align—
Ship the page; the build is fine. 🥕

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
  • 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.
• 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: ASSERTIVE

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 54e8164 and a51bafe.

⛔ Files ignored due to path filters (1)

• landing-page/package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (1)

• landing-page/package.json (1 hunks)

🔇 Additional comments (1)

landing-page/package.json (1)

43-43: All peer dependencies align; no mismatches detected

• eslint-config-next@15.5.0 requires
  • eslint ^7.23.0 || ^8.0.0 || ^9.0.0 — your ^9 declaration satisfies this
  • typescript >= 3.3.1 — your ^5 declaration satisfies this (TypeScript version in deps: ^5)
• Next 15.5.2 has no peerDependency on eslint-config-next that would conflict
• No config/schema errors are expected—installing devDependencies and running the linter should pass without rule mismatches

[NiveditJain]

Hey @JaclynCodes

Thanks for the PR.

Can you please explain the content to downgrade the version of eslint-config-next?

[JaclynCodes]

This pull request downgrades the eslint-config-next and its related dependencies from version 15.5.2 to 15.5.0 in the landing-page project. This affects both the main package.json and the lockfile, ensuring all references are consistent.

Dependency version downgrade:

• Downgraded eslint-config-next from 15.5.2 to 15.5.0 in both package.json and package-lock.json to ensure dependency consistency. [1] [2] [3]
• Downgraded @next/eslint-plugin-next from 15.5.2 to 15.5.0 in package-lock.json, following the main config downgrade. [1] [2]