Closed TheBlusky closed 11 months ago
lastversion
was created exactly to address this and the output seems actually correct here.
Author did not file formal release for 1.19.3, but it is not marked as pre-release, doesn't contain beta keywords, etc.
So https://github.com/n8n-io/n8n/releases/tag/n8n%401.19.3 is latest release :-)
In this case only raises question why they tagged 1.19.3 two weeks ago while the 1.18.2 one week later.
@TheBlusky maybe this issue should be about adding --formal
tag to only consider those as releases. I am not sure. So far, virtually in 99% cases tags as releases is the most reliable approach. Let me know what you think.
Oh, alright, I guess misunderstood the definition of release, my bad :-)
I use lastversion in a script for something like ~20 projects. I use it mainly to auto update images in docker-compose file. Usually, docker images of projects are updated using the same schema as projects release.
These two projects (my issues about n8n and cadvisor are now obviously the same issue), are the only ones I'm having issues with.
A --formal
option could solve my problems, and as you said, it's not needed for most of projects I'm following with this tool, but my help me for edge cases.
Added --formal
in v3.4.3
With this update, I was able to tweak my script with the formal
argument of latest()
.
Everything now works as expected for both projects. Thanks for this fast update !!!
Project with incorrect version
https://github.com/n8n-io/n8n
To Reproduce
Expected behavior
1.18.2
(Tag 1.19.3 exists, but latest release is 1.18.2 and latest pre-release is 1.20.0, I don't know why current output is 1.19.3)Program output
1.19.3
Support This Project
:heart: Love this project? Consider supporting us by becoming a GitHub Sponsor. GitHub Sponsors get priority attention to their issues and requests. Click here to sponsor.