[BUG] Windows CLI download link on website returns 404

[Varadraj75]

Describe the bug.

The Windows download link for AsyncAPI CLI on the official website is broken.

When installing the CLI from:
https://www.asyncapi.com/tools/cli

the Windows link redirects to:
https://github.com/asyncapi/cli/releases/latest/download/asyncapi.x64.exe

This URL returns a 404 Not Found error because the file does not exist in the GitHub release assets.

Due to this, Windows users are unable to download and install the AsyncAPI CLI using the website instructions.

Expected behavior

The Windows download link on the AsyncAPI CLI website should redirect to a valid GitHub release asset.

Clicking the link should successfully download the AsyncAPI CLI Windows executable, allowing users to install and use the CLI without encountering a 404 error.

Screenshots

How to Reproduce

1. Open https://www.asyncapi.com/tools/cli
2. Navigate to the Windows installation section
3. Click on the Windows download link for the AsyncAPI CLI
4. The link redirects to GitHub and shows a 404 Not Found error

🖥️ Device Information [optional]

• Operating System (OS): Windows 10
• Browser: Google Chrome
• Browser Version: Latest stable

👀 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]

hey @Souvikns @Shurtu-gal @AayushSaini101 .
Could you please check this? The Windows CLI download link returns a 404.
Let me know how we can proceed to fix this.

[Shurtu-gal]

Its due to this: #1975 (comment)

[Shurtu-gal]

Still investigating the issue.

[Varadraj75]

Thanks for the context
please let me know how I can help once the investigation is complete.

[Varadraj75]

@Shurtu-gal ,
Windows release jobs fail because CI is still using Node 20, while @asyncapi/cli@5.0.6 and @asyncapi/generator now require Node ≥24 and npm ≥11.
Local reproduction confirms npm ci fails/hangs on Node 20 but succeeds on Node 24.
Updating workflows to use .nvmrc / Node 24 fixes the issue.

[Shurtu-gal]

Great find @Varadraj75
Could you create a PR fixing this.

Also please check other workflow for the same as well.

For setting node version, you can take release workflow as reference.

[Varadraj75]

@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!