Update Node.js version in release workflow

[lirantal]

User description

Description

Release should move to a current LTS version for Node

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Checklist:

• I have updated the documentation (if required).
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.
• I added a picture of a cute animal cause it's fun

---

PR Type

Enhancement

---

Description

• Update Node.js version from 18.x to 24.x in release workflow

• Aligns with current LTS version requirements

---

Diagram Walkthrough

flowchart LR
  A["release.yml<br/>Node.js 18.x"] -- "upgrade version" --> B["release.yml<br/>Node.js 24.x"]

Loading

File Walkthrough

	Relevant files
Configuration changes	release.yml Update Node.js version to 24.x                                                      .github/workflows/release.yml Updated Node.js version from 18.x to 24.x in the setup-node action Ensures release workflow uses current LTS version +1/-1

---

[qodo-code-review]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
Update

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-code-review]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
General	Add npm cache to setup-node Add cache: 'npm' to the setup-node action to enable dependency caching, which will speed up workflow execution. .github/workflows/release.yml [21-23] - uses: actions/setup-node@v3 with: node-version: 24.x + cache: 'npm' Apply / Chat Suggestion importance[1-10]: 7 __ Why: This is a valuable performance optimization that correctly suggests adding npm caching to the setup-node action, which will speed up the workflow by caching dependencies.	Medium
	Use LTS alias instead of fixed version Replace the hard-coded Node.js version 24.x with the lts/* alias to automatically use the current Long-Term Support release. .github/workflows/release.yml [23] -node-version: 24.x +node-version: lts/* Apply / Chat Suggestion importance[1-10]: 6 __ Why: This is a good suggestion for improving maintainability by ensuring the workflow automatically uses the latest LTS Node.js version, reducing the need for future manual updates.	Low
More

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.01%. Comparing base (97d7adf) to head (2f3c922).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #211   +/-   ##
=======================================
  Coverage   98.01%   98.01%           
=======================================
  Files          13       13           
  Lines         404      404           
  Branches       96       96           
=======================================
  Hits          396      396           
  Misses          8        8           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.