Upgrade from old releases
Upgrading after skipping many revisions can be risky. Database migrations and other code are written and tested sequentially. Skipping many can surface untested combinations.
Find your current revision
To see what revision (rev) you have installed, run the following command:
Example below (with real data from the stable channel)
How to upgrade
Assuming that run the stable channel (you should), the latest revision is 226. Any update before 223 is blocked. This should only happen if you have manually disabled automatic updates, if this is the case please read the news carefully.
You need to upgrade to an intimidate version, for example if your current version is 221, you need to upgrade to 222, then 224 and finally 226 (less than 3 revisions each time).
Danger
If you try to upgrade directly from a revision before 223 to 226, updates will be blocked.
Note
The block functionality was implemented in revision 228, but everything else here is still true. If you have disabled automatic updates, please do not upgrade to many revisions at once.