Why is it difficult to find the newly minted version number?

[russellkg]

Describe the problem/error/question

When I started using n8n, it would tell me when there was a new version. I could click a link, and it would show me the new stable version number. I could update my compose file, run a few commands, and I’d be up with the new version.

Now, I have to find the new version number.

Can we display the new version number(s) within n8n again? This has caused updating to take longer. Not much, but as we all know, little increases in time to done result in large amounts of wasted time that don’t have to be.

Or am I missing it?

[mohamed3nan]

Hi @russellkg,

If you’d like to stay up to date without manually checking version numbers, you can use the Docker image tag n8nio/n8n:latest or n8nio/n8n:stable

https://hub.docker.com/r/n8nio/n8n/tags

Pulling either of these will automatically give you the newest stable release.

[jabbson]

This is how I see the version:

[russellkg]

I realize that.

I was also told that it isn’t the best practice since one may need to restart a system for various reasons, and having “latest” might trigger an unintentional update, which could have significant unintended consequences.

For this reason, I’ve been manually updating my compose file for each version, then running the commands to update my containers.

[russellkg]

I see.

The words “1 version behind” did not look like a link to me. Thank you for the boot to the head.