Nextcloud Server

166 stable versions known, 23.0.0 to 35.0.1. Data checked 43 minutes ago.

Required stops

• 23.0.12

  Latest 23.x release.

  Nextcloud must be upgraded step by step:

  • Before you can upgrade to the next major release, you need to upgrade to the latest point release of your current major version.
  • Then run the upgrade again to upgrade to the next major release’s latest point release.
  • You cannot skip major releases. Please re-run the upgrade until you have reached the highest available (or applicable) release.
  • Example: 18.0.5 -> 18.0.11 -> 19.0.5 -> 20.0.2

  Wait for background migrations to finish after major upgrades. After upgrading to a new major version, some migrations are scheduled to run as a background job. If you plan to upgrade directly to another major version (e.g. 24 -> 25 -> 26) you need to make sure these migrations were executed before starting the next upgrade. To do so you should run the cron.php file 2-3 times, for example:

  $ sudo -E -u www-data php -f /var/www/nextcloud/cron.php

  Source: https://docs.nextcloud.com/server/latest/admin_manual/maintenance/upgrade.html (checked 2026-09-26)

• 24.0.12 Latest 24.x release. Same rule as 23.0.12.
• 25.0.13 Latest 25.x release. Same rule as 23.0.12.
• 26.0.13 Latest 26.x release. Same rule as 23.0.12.
• 27.1.11 Latest 27.x release. Same rule as 23.0.12.
• 28.0.14 Latest 28.x release. Same rule as 23.0.12.
• 29.0.16 Latest 29.x release. Same rule as 23.0.12.
• 30.0.17 Latest 30.x release. Same rule as 23.0.12.
• 31.0.14 Latest 31.x release. Same rule as 23.0.12.
• 32.0.15 Latest 32.x release. Same rule as 23.0.12.
• 33.0.9 Latest 33.x release. Same rule as 23.0.12.
• 34.0.4 Latest 34.x release. Same rule as 23.0.12.

Sources

• github.com/nextcloud/server/releases
• docs.nextcloud.com/server/latest/admin_manual/release_notes/upgrade_to_26.html (quoted on routes that reach 26.0.0)
• docs.nextcloud.com/server/latest/admin_manual/release_notes/upgrade_to_27.html (quoted on routes that reach 27.0.0)
• docs.nextcloud.com/server/latest/admin_manual/release_notes/upgrade_to_28.html (quoted on routes that reach 28.0.0)
• docs.nextcloud.com/server/latest/admin_manual/release_notes/upgrade_to_30.html (quoted on routes that reach 30.0.0)
• docs.nextcloud.com/server/latest/admin_manual/release_notes/upgrade_to_31.html (quoted on routes that reach 31.0.0)
• docs.nextcloud.com/server/latest/admin_manual/release_notes/upgrade_to_32.html (quoted on routes that reach 32.0.0)
• docs.nextcloud.com/server/latest/admin_manual/release_notes/upgrade_to_33.html (quoted on routes that reach 33.0.0)
• docs.nextcloud.com/server/latest/admin_manual/release_notes/upgrade_to_35.html (quoted on routes that reach 35.0.0)

Nextcloud's GitHub release notes are lists of merged pull requests and mark nothing as breaking. What is quoted instead is the admin manual's “Critical changes” page for each major version (Upgrade to Nextcloud 26, 27, 28, 30, 31, 32, 33 and 35; there is none for 29 or 34), one item per section, labelled “Critical change”, on the x.0.0 release. The manual has no such pages before 26. Versions are covered from 23.0.0; GitHub has no complete release list before that. Required stops are the latest point release of each major version on the way, per the manual's upgrade page.