Track GitHub or npm for stable releases?

I am the maintainer of Cloudron n8n package. Recently, it was brought to our attention that we are tracking the incorrect n8n stable release. Currently, we are tracking the npm releases.

There is a discrepancy between Releases · n8n-io/n8n · GitHub and https://www.npmjs.com/package/n8n?activeTab=versions . Currently, GitHub says 1.112.6 is stable but npm says it is 1.113.3 . What should we use?

Thanks!

3 Likes

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..

1 Like