-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The latest release is not the latest #71
Comments
OK, good to know! |
Just as a reference this is the "failing" version command: https://github.com/nextcloud/vm/blob/master/lib.sh#L74 |
It chooses the first in the list:
|
@timar Can you please release 1.12.29? But release 1.11.29 first so that 1.12.29 become the "latest release"? |
I tried to do what you suggested, but in fact the time of the tag creation counts, not the time of actual release creation. Anyway, now the latest release is 1.12.29, because I removed 1.11.29. Next time I'll make the version 11 tag first. |
Thank you! |
In the Nextcloud VM scripts we fetch the latest release with Github API. This means that we currently fecth 1.11.28 when we really should fetch 1.12.28. This causes the script to fail becuase 1.11.28 is not compatible with Nextcloud 12.
Please always release the latest version last. Thanks!
If possible, make a new release that's compatible with Nextcloud 12.
cc @timar
The text was updated successfully, but these errors were encountered: