If you don't supply an explicit version to download, --version-to xx.yy
, then owut
goes through a series of checks to determine what it should do. See https://openwrt.org/docs/guide-user/installation/sysupgrade.owut#selecting_a_version for full details, but the short version is "it does what you expect."
First, it always stays on the current branch, you must force it to jump that major version boundary (for example, if you are on 24.10.5, and 25.08.0 comes out, owut
will stick with 24.10). Second, if you are on any snapshot (main or release), it will stay on that forever, until you force it.
Last, owut
sorts the list of versions, RCs come first, then releases by minor rev number, and selects the "latest". Run owut versions
and you'll see all of this in action; here it is for one of my test routers that currently has 24.10.0-rc4 installed (note that parenthetical list after that version number):
$ owut versions
owut - OpenWrt Upgrade Tool 2024.12.10~e38844ae-r1 (/usr/bin/owut)
Available 'version-to' values:
23.05 release branch
23.05.0
23.05.2
23.05.3
23.05.4
23.05.5 (latest)
23.05-SNAPSHOT
24.10 release branch
24.10.0-rc1
24.10.0-rc2
24.10.0-rc3
24.10.0-rc4 (latest,installed,requested)
24.10-SNAPSHOT
SNAPSHOT main branch
SNAPSHOT (latest)
As soon as 24.10.0 is released, it will occupy the spot after the final -rcn and become "latest".
See the cron job posts above, be sure to read the warnings. @Klemen86 reported success just last week...