[BUG] Release workflow fails because Node 18 is still declared in .nvmrc and engines

[Varadraj75]

Describe the bug.

The release workflow Publish to any of NPM, Github, and Docker Hub is currently failing because the project still declares Node 18 as the required version via:

• .nvmrc = v18
• "engines": { "node": ">=18" } in package.json

As a result, the release job runs on Node v18.20.8, but some dependencies (for example yargs-parser@22) now require a minimum Node.js version of 20.

This causes the release step to fail with the following error:

  yargs parser supports a minimum Node.js version of 20
  current: { node: 'v18.20.8' }

The failure happens consistently in the release job after merge.

Expected behavior

The release workflow should resolve and run on Node.js >= 20, so that it is compatible with current dependencies and the job completes successfully without engine/version errors.

Screenshots

The release job fails on Node v18.20.8 while yargs-parser requires Node >= 20, as shown below.

How to Reproduce

1. Clone the repository:

   git clone [https://github.com/asyncapi/modelina.git](https://github.com/asyncapi/modelina.git)
   cd modelina

2. Trigger the release workflow:
   Push or merge a commit to the master branch that meets the conventional commit criteria (e.g., a message starting with fix: or feat:).

3. Navigate to GitHub Actions:
   Open the workflow run specifically for:

   • Workflow: Release (Node project)
   • Job: Publish to any of NPM, Github, and Docker Hub

🖥️ Device Information [optional]

• Operating System (OS): macOS
• Browser: N/A
• Browser Version: N/A

👀 Have you checked for similar open issues?

• I checked and didn't find similar issue

🏢 Have you read the Contributing Guidelines?

• I have read the Contributing Guidelines

Are you willing to work on this issue ?

Yes I am willing to submit a PR!

[Varadraj75]

@jonaslagoni , i have opened a PR to fix this issue.
would really appreciate your review when you have time.

[giruuuuj]

hi
Issue: #2417 - Release workflow fails due to Node.js version mismatch
PR: #2418 - chore: bump Node.js requirement to >=20

Root Cause Analysis ✅
The release workflow fails because:

.nvmrc still pins Node.js v18
package.json engines field allows >=18
Dependencies like yargs-parser@22 now require Node.js >=20
CI runs on Node 18, causing engine compatibility errors
Solution Implemented 🛠️
Minimal, targeted changes:

Updated .nvmrc from v18 → v20
Updated package.json engines from ">=18" → ">=20"
Ensured consistency with GitHub Actions workflow
Impact & Benefits 🚀
Fixes CI/CD: Release workflow now runs successfully
Future-proofs: Aligns with modern Node.js ecosystem requirements
Zero breaking changes: Only affects development/CI environment
Tested locally: All tests pass on Node.js v20.20.0
Why This Is a Good Contribution
✅ Clear problem identification with specific dependency conflicts
✅ Minimal risk - only configuration changes, no code modifications
✅ Complete fix - addresses both .nvmrc and package.json consistency
✅ Well-tested - verified locally with full test suite
✅ Follows conventions - uses conventional commit type chore:

This change ensures the Modelina project's release pipeline remains stable as the Node.js ecosystem evolves. The PR is ready for review and merge.