fix: windows release by aligning Node version with engine requirements

[Varadraj75]

Description

• Fixes Windows release failures by aligning CI Node.js version with current engine requirements (Node ≥ 24, npm ≥ 11).
• Updates the release asset upload workflow to use the correct Node version, preventing missing Windows .exe artifacts.
• Ensures CI behavior is consistent with the release workflow and local development setup.

Related issue(s)

Resolves #1982

[changeset-bot]

⚠️ No Changeset found

Latest commit: 5d34899

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

[Copilot]

Pull request overview

This PR aims to fix Windows release failures by aligning the CI Node.js version with the engine requirements specified in package.json (Node ≥24). The change updates the Windows asset upload workflow to use .nvmrc for determining the Node version instead of the hardcoded Node 20.

Changes:

• Updates the Windows build step in the release asset upload workflow to read Node version from .nvmrc file instead of using a hardcoded version

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Varadraj75]

hey @Shurtu-gal ,
I have opened a PR fixing the CI Node version issue all relevant tests are passing
would appreciate a review when you have time. Thanks!

[Shurtu-gal]

Please have a look at other workflows as well in case we are missing node version fix.

[Shurtu-gal]

I don't think we have nvmrc file.

You can use this instead.

cli/.github/workflows/release-with-changesets.yml

Lines 95 to 105 in 870eb6b

	- if: steps.packagejson.outputs.exists == 'true'
	name: Check package-lock version
	uses: asyncapi/.github/.github/actions/get-node-version-from-package-lock@master
	id: lockversion
	with:
	node-version: ${{ vars.NODE_VERSION }}
	- if: steps.packagejson.outputs.exists == 'true'
	name: Setup Node.js
	uses: actions/setup-node@v6
	with:
	node-version: "${{ steps.lockversion.outputs.version }}"

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[Varadraj75]

Sorry about that @Shurtu-gal — I missed cross-checking this earlier.

I have now updated the workflow to remove the .nvmrc usage and aligned the Node version setup with the pattern used in release-with-changesets.yml. All checks are passing, and I also verified the fix locally.

Could you please take another look when you have time? Thanks!