Fix: Update Node.js Engine Requirement for Frontend to Match Dependency Needs

[Amitjoiya]

🔧 Fix: Update Node.js Engine Requirement

📌 Summary

This PR updates the frontend application's required Node.js version to resolve errors encountered during linting and ensure compatibility with current project dependencies.

🛠 Issue

When using Node.js 18.17.0, running npm run lint causes an error:

Next.js requires Node.js version "^18.18.0 || ^19.8.0 || >= 20.0.0"

This prevents linting and may block other development tasks.

🚀 Changes Made

• Updated Node version in "engines" field of package.json
• Reinstalled dependencies to ensure compatibility

(Optional if needed)

• Updated CI workflow configuration to use compatible Node.js version

🧪 Tested Scenarios

Action	Result
npm install	✔ Successful
npm run lint	✔ No version error
npm run dev	✔ Runs normally

🔗 Closes Issue:

Closes: #1265

Summary by CodeRabbit

• Chores
  • Updated Node.js runtime version to 20.18.1 across GitHub Actions CI/CD workflows for improved environment consistency.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Four GitHub Actions workflows updated to specify Node.js version 20.18.1 instead of generic version 20, addressing dependency compatibility requirements without changing workflow logic.

Changes

Cohort / File(s)	Summary
Node.js version updates in CI/CD workflows .github/workflows/hexabot-npm.yml, .github/workflows/pull_request.yml, .github/workflows/release.yml, .github/workflows/widget-npm.yml	Updated Node setup step to use specific patch version "20.18.1" instead of generic "20" or numeric 20, ensuring consistent Node.js environment across all CI workflows

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Homogeneous, repetitive changes applied uniformly across 4 workflow files with no logic modifications
• Simple version string updates with no functional impact on workflow behavior

Possibly related PRs

• docs: update node 20 #1425: Updates Node.js version to 20.18.1 in README prerequisites documentation alongside this workflow update
• fix: update node version to node v20 deps #1404: Also modifies Node.js version in the same GitHub Actions workflow setup-node steps

Suggested labels

needs-review

Suggested reviewers

• medchedli
• MohamedAliBouhaouala
• marrouchi

Poem

🐰✨ A rabbit hops with glee today,
Node twenty dot eighteen point one's on its way,
Dependencies aligned, no more dismay,
The workflows dance in harmony's display!

Pre-merge checks and finishing touches

❌ Failed checks (2 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The PR description covers motivation, issue, changes made, and testing scenarios but does not follow the provided template structure with explicit sections for Type of change and Checklist items.	Align description with the template by explicitly including Type of change section and completing the Checklist with checkmarks for self-review, testing, and other applicable items.
Linked Issues check	❓ Inconclusive	The PR addresses the core requirement from #1265: updating Node.js version to satisfy Next.js dependencies (20.18.1 meets >=20.0.0 requirement) and updating CI workflows, though the package.json engine field update is not visible in file changes.	Clarify whether package.json engine field was updated as mentioned in PR description; confirm Node.js 20.18.1 resolves the linting issue for all workspace components.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: updating Node.js engine requirement for frontend to match dependency needs, which aligns with the PR's core objective of resolving linting errors.
Out of Scope Changes check	✅ Passed	All file changes (four GitHub Actions workflows) directly support the PR objective of updating Node.js version configuration to resolve dependency compatibility issues across CI pipelines.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

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

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0f6c902 and b062f28.

📒 Files selected for processing (4)

• .github/workflows/hexabot-npm.yml (2 hunks)
• .github/workflows/pull_request.yml (2 hunks)
• .github/workflows/release.yml (2 hunks)
• .github/workflows/widget-npm.yml (2 hunks)

🔇 Additional comments (4)

.github/workflows/hexabot-npm.yml (1)

19-19: Node.js version consistently updated to match dependency requirements.

The change from generic "20" to the specific patch version "20.18.1" is appropriate and aligns with the PR objective to resolve Next.js compatibility. This version satisfies the required semver range (>= 20.0.0).

Also applies to: 51-51

.github/workflows/release.yml (1)

18-18: Node.js version consistently updated in both test workflows.

The updates in both Frontend-Tests and API-Tests jobs use the same pinned version (20.18.1), ensuring reproducible CI behavior and satisfying the Next.js version requirements.

Also applies to: 52-52

.github/workflows/widget-npm.yml (1)

19-19: Node.js version consistently updated to match dependency requirements.

The change from generic "20" to the specific patch version "20.18.1" maintains consistency across the publishing workflows and ensures the widget package builds with a compatible Node.js version.

Also applies to: 51-51

.github/workflows/pull_request.yml (1)

18-18: Node.js version updated to resolve linting failures in PR validation.

The change to "20.18.1" in both Frontend-Tests and API-Tests directly addresses the reported issue where npm run lint was failing with the Node.js 18.17.0 requirement error. This version satisfies Next.js engine requirements and enables lint-staged and ESLint checks to run successfully.

Also applies to: 51-51

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Amitjoiya]

@maintainers Please review, Thanks!