-
Notifications
You must be signed in to change notification settings - Fork 33
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
Updating from 25.0.0 beta5 to beta6 shows no update #436
Comments
@PVince81 can you reproduce with |
|
oh, updater version beta3 ?? from the beta5 tarball:
beta6 tarball:
|
It works for me when i switch to stable channel and switch back to beta channel. |
This is what I get on the command line, but let me try this channel switching Blizzz talks about...
To be clear, the "upgrade process" takes 0.1 sec to run and doesn't actually do anything, am still on beta 6 of course…. |
is already latest |
that refers only to the last time the updater was build. But it is confusing, yes. |
I think originally the updater was not intended to be tagged like the server repo and bundled apps, for it is not build each time. |
I could reproduce it only in one of four attempts. I want to blame browser cache… It should not bug you for more then 30minutes though, for that is how long the result from the updater server is cached. During installation, the timestamp is saved, with an empty result, i.e. in that case nothing should be offered you in the 30minutes after installation. To reset the timestamp, run |
Ah, one another thing is: if the release channel is not set in config.php, the updater defaults to stable, therefore the empty result. Nextcloud server itself defaults to whatever is set in version.php, and that's beta. This is why toggling stable and beta works is the workable workaround. It was always ™️ like it, thanks for finally filing :D |
in my local dev setup switching the channel to stable then back to beta, and then running this made the updater go through! |
Steps
Expected
Update available both on settings page and inside the updater
Actual
@blizzz
The text was updated successfully, but these errors were encountered: