We’re running the docker container with the “latest” tag, but often seem to be a version or two behind (even though a fresh pull shows we’re running the latest docker image).
Did see a related earlier thread that is now closed that said it was an issue being investigated. Wondering if anyone has new or additional info.
Ah btw. for some reason I mixed up the threads. I thought you referred to this this one. I will comment on the one you actually linked to avoid any confusion for other users in the future. Thanks for making us aware of it!
I’m thinking maybe the solution here is correcting the wording in the UI. The UI implies that we are running behind on updates and need to update.
“You’re on 1.54.4, which was released 6 days ago and is 1 version behind the latest and greatest n8n”
Which by your definition of versioning (latest vs next), we are 1 version behind the latest which would imply we aren’t current on updates.
Instead there should not be a ‘1 update’ icon and instead the notifications pop out should say:
“Congrats, you are running 1.54.4 which is the latest. If you want to try out the next version, 1.55.3 is available for testing.”
In this update it actually looks like we accidentally hit the wrong box which pushed the next as latest. Normally we would only show the latest tagged version not the next.
I’m having a hard time understanding this answer, as the chief complaint here is the exact same as what I had reported previously, only without the explanation of the difference between Latest/Next, my Question appeared to be an issue with your build pipeline not correctly tagging what is actually the latest. And with no follow up to that question, I can only assume it was never resolved and here we are again with the same issue still occurring.
