I could still update manually, so it’s not a big deal, but as time is not free, and the eecms updates have worked quickly and (mostly) painlessly in the past, the question is: can I set eecms to update only to the last revision of the 5.x branch?
can you clarify the steps you’ve been taking to update “over SSH”? SSH is really just the protocol your using to connect to the host. Are you uploading the files through rsync or sftp and SSH and then going to the site to run the upgrader or maybe logging in to the host and then using CLI?
If you just want to quickly get to the latest version of 5 (5.4.2), then you can log in to the CP and use the 1-click updater. It will require you to update to 5.4.2 first, then won’t let you go to 6.x unless you authorize.
Allow me to quote myself:
> updating over SSH with eecms
eecms being the binary used to upgrade, to wit:
system/ee/eecms upgrade -v
Which then gives me a reasonably detailed output of what’s happening, as it happens–unlike most 1-click thingies in the world.
(And yes, “over SSH” really means “by way of an SSH connection to the host”.)
sorry about that, not enough coffee yet for Monday morning. lol
Just for others who might come here, as you probably discovered the
eecms tool follows the 1-click upgrader functionality in requiring the user to update to the latest version of 5 first (currently 5.4.2).
Also note that in v6, the
eecms tool has been superseded by the new CLI tool which has more options available in the update process.
We also announced recently that the CLI will be updated to include add-on and migrations generators in 6.1.