Older n8n version marked as "latest" on https://github.com/n8n-io/n8n/releases

[markup]

Hi!
I have built a workflow which checks if there are newer n8n versions than the instance it is running in.
In order to get the latest n8n version, I’m performing a HTTP request of https://api.github.com/repos/n8n-io/n8n/releases/latest.
As of 2025/11/05 11:00:00 CET, the response shows version 1.117.3 as latest.
However, the release notes of Release notes | n8n Docs tell me, version 1.118.1 is currently latest.
Also, Releases · n8n-io/n8n · GitHub mark the older version as latest, but 1.118.1 as “pre-release”.
Is it possible to keep release notes in documentation and github synchronized?

[mohamed3nan]

I think the reason behind it is:

Track GitHub or npm for stable releases?

Yes indeed! I found this action: Release: Push to Channel · Workflow runs · n8n-io/n8n · GitHub It’s the workflow that sets latest/stable tags on npm, updates Docker/GHCR images, and triggers docs updates. So the “latest” seen on npm/Docker/docs comes from here, not GitHub Releases itself, which can still show a pre-release..

So i just use the npm registry link:

https://registry.npmjs.org/n8n/latest

This will give you the latest n8n version without delays..

[markup]

Thanks for the quick reply and the solution!

[markup]

Yesterday I was proven that https://registry.npmjs.org/n8n/latest definitely is the way to go.
It said 1.119.1 is the latest version, so I updated my n8n instance and it fetched exactly that version. Release notes and Github still marked 1.118.2 as latest.
Today, almost 24 hours later, release notes still say 1.118.2 is latest, but Github (already) shows 1.119.1