Updating from 13.1.0-RC2 to stable is not available
When I switched to stable, the script detects the stable release of 13.1.0 but it does not offer a way to do the update.
However if I switch it back to beta, I can see and click to update to the latest beta release of 14.
Now I don't mind updating directly to the latest beta from my current versioning, but would that produce errors if I totally skip 13.1.0 stable?
-
Hello @LoneTreeLeaf !
Yes, you need to process all "beta" steps after 13.1.0-RC2. For now, you have left 13.1.0-RC3 and 13.1.0.
-
Sorry, reviewing the documentation doesn't really help me as it's very vague, what do you mean by process all the beta steps?
I see there's upgrade packages on the GIT repo, is that what you mean? If so, how would I go about applying these one by one?
-
Or do you mean I'm OK to click to process the update while on the beta channel? I've never version updated when there is more than 1 version updates available, does the script automatically go through them one by one?
-
Yes, you will need to stay on the beta channel. Then press the Upgrade button in your Dashboard - you will be informed that upgrade to 13.1.0-RC3 has started. Follow the appearing instructions - it means you will need to upgrade all installed modules too. After that "upgrade step" will be completed. Then you will need to repeat the procedure for the next, 13.1.0 step.
-
Understood, so if I'm understanding this process correctly.
Perform a full backup of my UNA instance just to be safe. (Already done.)
Perform the first upgrade.
Perform all module upgrades.
Repeat until on stable.
Is this correct? Sorry for the onslaught of questions, just wanna make sure I do this safely.
-
Disregard my last question, updates are going smoothly, thank you for your help @LeonidS!
-
Seems I spoke too soon, making my way up to the latest alpha, currently on A2 of UNA 14, and I get the following error for this apps.
Download Error
-
Technology is weird, resolved itself on its own after I deleted the Files app (was deactivated as I wasn't currently using it on the live site), re-installed it just to have it, disabled it again, and then all the other upgrades went through without a hitch.
-
Yes, you're correct :-)
