SSD Nodes Learn Hosting plans →
Guides Matt ConnorBy Matt Connor

do-release-upgrade: no new release found

Your Ubuntu server reports no new release found. Work through the Prompt setting, the LTS point release gate, third party repos and held packages.

Why do-release-upgrade says no new release found

do-release-upgrade ending in No new release found. is almost never a broken tool. The path you asked for is closed at that moment, and the tool reports that in the shortest way it can. Five things close it: the Prompt setting in /etc/update-manager/release-upgrades, the point release gate on LTS (long term support) upgrades, third party repositories, packages that are held or half configured, and a release that is past its end of support and whose packages have left the main archive.

Work through them in that order. Each one has a command that proves whether it applies to your server, so you never have to guess which of the five you are looking at.

What the check-only flag actually reports

sudo do-release-upgrade -c
echo $?

-c is check only. It reads Canonical's release metadata over HTTPS (hypertext transfer protocol secure) and prints the answer. It downloads no upgrade tool and rewrites no source file. Two outputs matter:

Checking for a new Ubuntu release
No new release found.
Checking for a new Ubuntu release
New release '26.04.1 LTS' available.
Run 'do-release-upgrade' to upgrade to it.

On an LTS release with Prompt=lts, the first answer is worded differently. The upgrader's source prints There is no development version of an LTS available. whenever Prompt=lts is set and nothing is found, even if you never passed -d. It means the same thing as No new release found.

The exit code carries the same answer for scripts. It is 0 when a release is available and 1 when none is. That follows the usual shell convention of zero for success, so a script can treat a zero exit as "a new release is on offer".

If your login banner still shows the old answer, it is cached. That line comes from /etc/update-motd.d/91-release-upgrade, which hands over to /usr/lib/ubuntu-release-upgrader/release-upgrade-motd, and that helper works from the text stored in /var/lib/ubuntu-release-upgrader/release-upgrade-available. Running the helper yourself does not give you a fresh answer. Within a day of the last check it reprints whatever text is stored and asks nothing. Once the stored text is a day old, or when there is no stored file and the helper runs as root, it starts /usr/lib/ubuntu-release-upgrader/check-new-release -q in the background, writes that check's output into the stored file, and prints nothing itself. Either way, what the banner shows is never the result of a check made at that login. To clear a stale banner, delete the stored file with sudo rm /var/lib/ubuntu-release-upgrader/release-upgrade-available, and the next login starts a fresh check. For the answer itself, just trust -c. The banner only repeats the result of the last check that ran.

The check also needs to reach changelogs.ubuntu.com. On a server behind a strict outbound firewall or a proxy the tool cannot ask, so it cannot find anything.

curl -sI https://changelogs.ubuntu.com/meta-release-lts | head -n 1

A HTTP/2 200 line means the server can see the metadata. No output at all means the request failed, because -s also hides curl's error message, so run echo $? straight afterwards. Exit code 6 means the name did not resolve. Exit code 7 (failed to connect) or 28 (timed out) usually points at your egress rules or proxy, though a slow DNS lookup also counts against curl's connect timeout. Whichever it is, no amount of editing APT (advanced package tool) files will change the answer.

If the command is missing entirely, it lives in ubuntu-release-upgrader-core. Minimal cloud images sometimes leave that package out.

sudo apt install ubuntu-release-upgrader-core

Read /etc/update-manager/release-upgrades before changing anything

cat /etc/update-manager/release-upgrades
[DEFAULT]
Prompt=lts

The file carries its own documentation in comments. Three values are valid:

  • never: never check for, and never allow, an upgrade to a new release.
  • normal: offer the supported release that immediately follows the running one.
  • lts: offer the first LTS release that follows the running one.

Prompt=never is the easiest of the three to diagnose, because the tool names both the file and the setting in its output:

Checking for a new Ubuntu release
In /etc/update-manager/release-upgrades Prompt
is set to never so upgrading is not possible.

Hosting providers and configuration management tools set never deliberately, to stop a fleet drifting between releases. If you find it there, someone chose it. Change it to lts for a server you want on the long term support track, and put it back afterwards if your automation expects the old value.

One detail in those comments catches people out. When Prompt=lts is set and the running release is not itself an LTS release, the upgrader treats the setting as normal. On a 25.10 machine the two values behave identically. On a 24.04 machine they read different files, and that difference is the whole of the next section.

Why an LTS to LTS upgrade waits for the first point release

Prompt decides which metadata file the upgrader reads. The addresses live in /etc/update-manager/meta-release:

[METARELEASE]
URI = https://changelogs.ubuntu.com/meta-release
URI_LTS = https://changelogs.ubuntu.com/meta-release-lts
URI_UNSTABLE_POSTFIX = -development
URI_PROPOSED_POSTFIX = -proposed

Prompt=lts reads meta-release-lts. Prompt=normal reads meta-release. Both files describe every release in a small block of keys, and the upgrader offers a release only when its Supported: flag is 1. Read them yourself, from the same server:

curl -s https://changelogs.ubuntu.com/meta-release-lts | grep -A 4 resolute
curl -s https://changelogs.ubuntu.com/meta-release | grep -A 4 resolute

Checked on 27 October 2026, the two files agree about Ubuntu 26.04. The LTS file says:

Dist: resolute
Name: Resolute Raccoon
Version: 26.04.1 LTS
Date: Thu, 23 April 2026 00:26:04 UTC
Supported: 1

The plain file says:

Dist: resolute
Name: Resolute Raccoon
Version: 26.04.1 LTS
Date: Thu, 23 April 2026 00:26:04 UTC
Supported: 1

They did not always agree. On 13 August 2026 the LTS file still listed Version: 26.04 LTS with Supported: 0, while the plain file already carried Supported: 1. That 0 in the LTS file was the gate. A 24.04 server using the default Prompt=lts read that file, found no newer LTS release marked available, and reported that there was nothing to upgrade to. Nothing on the machine was wrong. Canonical had not opened the path yet.

The flag flips to 1 when Canonical enables LTS upgrades. That comes after the first point release, not on the day it ships, and for 26.04 it has happened. Ubuntu 26.04.1 was released on 27 August 2026, and on 29 September 2026 Canonical announced that upgrades from 24.04 "are now enabled". The LTS file now marks 26.04.1 supported, so a 24.04 server on Prompt=lts is offered 26.04.1 and the gate is no longer a reason for an empty answer. If your 24.04 server still finds nothing, the cause is elsewhere on this page: a cached login banner, blocked access to changelogs.ubuntu.com, or Prompt=never. A point release is not a new version of Ubuntu, only the same release with every update since launch folded into fresh install media, so what matters to a running server is the gate that opens after it rather than the media itself. The delay is deliberate: the people who upgrade early find the blockers, and those get fixed before the much larger population of LTS servers follows. Canonical's 26.04.1 announcement says the automatic offer through Update Manager would come "a couple of weeks following this release after some planned backports to address regressions in a recent version of rust-coreutils". For the details, what 26.04.1 shipped with and what it means for a 24.04 server picks the story up from there.

With the gate open, the old choice between waiting and switching to Prompt=normal no longer applies to this upgrade. Leave Prompt=lts in place and run sudo do-release-upgrade, which now targets the released 26.04.1. If you switched to normal while the gate was closed, set the value back to lts so the server stays on the long term support track. The procedure itself, step by step, is in the full 24.04 to 26.04 server upgrade walkthrough. A server still on 22.04 has an extra hop to make, because Prompt=lts only ever offers the next LTS release, so the route from 22.04 to 26.04 goes through 24.04 first.

Third party repositories and PPAs that block the upgrade

The upgrader rewrites your APT sources to point at the new release. By default it keeps Ubuntu's own archive and mirrors and comments out third party repositories, even ones that already publish for the new release. An entry it keeps is still disabled when it has no Release file for the new series. The reasons go to the upgrader's log, one line per entry, rather than to the screen, and they are specific: was disabled (unknown mirror), was disabled (unknown dist), and was disabled (no Release file).

A PPA (personal package archive) publishes separately for each Ubuntu series, and many publish for several at once. The graphics-drivers PPA, for example, lists both noble/ and resolute/ in its dists/ directory. A PPA whose owner has not built for resolute yet has no directory for it on the server, so even with third party sources allowed the upgrader cannot fetch a Release file for the new series and disables the entry. Open https://ppa.launchpadcontent.net/<owner>/<ppa>/ubuntu/dists/ in a browser to see which series yours carries. A missing series is usually a warning you can accept. It becomes a stop when a package you installed from that repository cannot move with the rest of the system. APT keeps one version of each package, chosen by priority subject to dependency constraints, and by default it does not downgrade an installed package. A PPA version newer than the one the new release ships therefore stays in place, and if it depends on library versions the new release no longer carries, the upgrade calculation fails.

Decide this yourself before you start, rather than letting the tool decide during a long unattended run.

ls /etc/apt/sources.list.d/
apt policy nginx
sudo add-apt-repository --remove ppa:example/ppa

apt policy on a package name prints, in the words of its manual, "detailed information about the priority selection of the named package": the versions APT can see, the repositories whose current indexes offer each one, and their priorities. Run it on the packages you care about to see which ones the source you are about to disable currently supplies. It is not a record of where the installed copy came from, and it says nothing about which other packages depend on it. An installed version that only a PPA offers is a strong hint that it came from there, not proof. Removing the source does not downgrade anything, so a package installed from a PPA stays at its PPA version and can be newer than the new release carries. Where that matters, remove the package as well, and reinstall it from the archive after the upgrade. A repository you plan to bring back, such as Tailscale's, needs its codename updated to the new release before the package will install again, which is where most Tailscale install errors on Ubuntu come from.

There is a flag for the opposite choice. The manual page describes --allow-third-party as "Try the upgrade with third party mirrors and repositories enabled instead of commenting them out." Use it only when you have confirmed that the repository already publishes for the target release. If it does not, the flag either gains you nothing, because an entry with no Release file for the new series is disabled anyway, or keeps packages enabled that were never built for that release.

On Ubuntu 24.04 and later most sources live in /etc/apt/sources.list.d/ubuntu.sources in the deb822 format. The same repository written in both the old and the new format is a separate problem. On its own it only produces a warning that the target is configured multiple times, though two entries for the same source that set conflicting options do stop APT with an error. Both are covered in the duplicate source entry error in deb822 format.

Held and half configured packages stop the calculation

A release upgrade has to move almost every package on the system. If one package cannot move, the calculation fails, and the upgrader would rather stop early than leave you halfway. Two commands find the cause.

apt-mark showhold
sudo dpkg --audit

apt-mark showhold prints held packages one per line, and prints nothing at all on a clean system. A hold is a manual instruction never to change that package. Somebody pinned a kernel, or a database version, and then forgot. Release the ones you no longer need with sudo apt-mark unhold followed by the package name.

dpkg --audit lists packages that were unpacked but never configured. That state comes from an install that was interrupted, most often by a session that dropped. The upgrader tries to repair it and logs dpkg interrupted, calling dpkg --configure -a, but running the repair yourself first means you read the error instead of hunting for it afterwards. A package the tool cannot repair produces the message Package in inconsistent state, and that one needs attention before you retry.

Bring the running release fully current before you upgrade it.

sudo apt update
sudo apt full-upgrade -o APT::Get::Always-Include-Phased-Updates=true
sudo apt --fix-broken install
sudo dpkg --configure -a
sudo reboot

The phased updates option matters more than it looks. Ubuntu rolls some updates out to a percentage of machines at a time, so a plain apt upgrade can correctly leave packages behind, and the server is then less current than you believe. That option takes them all. Reboot afterwards if a kernel came with them, so you upgrade from the kernel you are actually running. A box that already keeps itself patched through unattended security upgrades has less to do here, though that mechanism never crosses a release boundary by design.

When the release is past end of standard support

An interim Ubuntu release is supported for nine months. When that support ends its Supported: flag goes to 0, but that alone does not close the path out of it. The upgrader skips unsupported releases only as targets, and Canonical's notice that 25.10 reached end of life on 9 July 2026 states: "The supported upgrade path from Ubuntu 25.10 is to Ubuntu 26.04 LTS." Checked on 27 October 2026, meta-release says this about 25.10:

Dist: questing
Name: Questing Quokka
Version: 25.10
Date: Thu, 09 October 2025 00:25:10 UTC
Supported: 0

What closes the path is the archive, and it moves later than the end of life date. The same notice said 25.10 would be archived to old-releases.ubuntu.com "in the coming weeks". Checked on 27 October 2026, questing was still on archive.ubuntu.com and not yet on old-releases.ubuntu.com, so a 25.10 server can still update and upgrade straight to 26.04 LTS. Once a release is moved, its packages are removed from archive.ubuntu.com and kept at old-releases.ubuntu.com. Then apt update starts returning 404 Not Found, the system can no longer be brought current, and because the upgrader insists on a current system, nothing proceeds. Fix the sources first.

lsb_release -cs
grep -rn ubuntu.com /etc/apt/sources.list /etc/apt/sources.list.d/

Point both archive.ubuntu.com and security.ubuntu.com at old-releases.ubuntu.com, and leave your codename alone. Only the host name changes.

sudo sed -i.bak -e 's/archive.ubuntu.com/old-releases.ubuntu.com/g' \
                -e 's/security.ubuntu.com/old-releases.ubuntu.com/g' \
                /etc/apt/sources.list.d/ubuntu.sources
sudo apt update

Run the same command against /etc/apt/sources.list instead if your server still keeps its sources in that single file. The -i.bak option writes a backup next to the original, so you can put it back if the edit was aimed at the wrong file. A clean apt update afterwards means the archive is reachable again, and do-release-upgrade will now talk to you.

Be realistic about how far this gets you. Ubuntu supports one release step at a time, so a server two or three dead releases behind needs every step in turn, and each step can fail on its own third party repository or its own held package. On a VPS it is often faster to build a new server on the current LTS, move the service across, and keep the old one until you are sure. That also gives you a rollback, which an in place upgrade never does. If you are choosing which track to sit on afterwards, the difference between LTS and interim releases on a server is worth reading before you decide.

What the development release flag really does

-d, or --devel-release, adds -development to the address of the file that Prompt selected, so the upgrader reads meta-release-development under Prompt=normal and meta-release-lts-development under Prompt=lts. It also lets the upgrader pick a release whose Supported: flag is still 0. The manual page describes it as "If using the latest supported release, upgrade to the development release."

Checked on 27 October 2026, the newest entry in meta-release-development is not 26.04:

Dist: stonking
Name: Stonking Stingray
Version: 26.10
Date: Thu, 15 October 2026 00:26:10 UTC
Supported: 0

The newest entry is not what the upgrader picks, though. It walks the file in order and takes the first release dated after the one you are running. On a 24.04 server that is resolute in both development files, so -d on 24.04 lands on the released 26.04.1, and Canonical's own 26.04.1 announcement tells 24.04 users who are "eager to make the jump" to run do-release-upgrade -d. Now that the LTS gate is open, a plain do-release-upgrade reaches the same release without the flag. On a 26.04 server the first newer entry is 26.10. Ubuntu released 26.10 on 15 October 2026, but checked on 27 October 2026 meta-release still ends at resolute, so a 26.04 server on Prompt=normal gets No new release found. from a plain check. Canonical's 26.10 announcement says users of 26.04 "will be offered an automatic upgrade to 26.10" if they chose to be notified of all releases, without giving a date. Until that entry appears, -d on 26.04 reaches the released 26.10 only through the development file, where it is still marked Supported: 0, ahead of the path Canonical has opened. The 26.10 release notes add that systems running under TPM-backed full disk encryption cannot upgrade from 26.04 to 26.10 at release. With Prompt=lts in place on 26.04, meta-release-lts-development lists nothing after resolute, and the flag stops with a message of its own:

There is no development version of an LTS available.

Ubuntu's server documentation is direct about the flag: "using the development release (or the -d flag) is not recommended for production environments". A development release changes daily and carries no security support promise, so a package that works in the morning can break a service in the afternoon. When -d points at a development release, use it on a scratch virtual machine you built to test your own configuration. Do not use it on a server anyone depends on. When you want the released 26.04 on a 24.04 server, a plain do-release-upgrade with Prompt=lts now gets you there.

Run the upgrade where a dropped SSH session cannot break it

A release upgrade replaces most of the system, including openssh-server and systemd. If your SSH (secure shell) session dies while dpkg is working, the process is killed with packages unpacked and unconfigured, which is exactly the state that stops your next attempt. If that has already happened to you, recovering an upgrade that stopped halfway is a separate job, and it comes before any second attempt. Start the upgrade inside a terminal multiplexer every time.

sudo apt install -y tmux
tmux new -s upgrade
sudo do-release-upgrade

If the connection drops, log back in and run tmux attach -t upgrade. The upgrade kept running, because it is a child of the tmux server rather than of your SSH session. screen -S upgrade and screen -r upgrade do the same job if you prefer screen.

The upgrader carries its own safety net for people who do not use a multiplexer. When it detects that it is running under SSH, it offers to start a second sshd on port 1022, so a broken main session still leaves a way in. It decides by walking its own parent processes looking for one called sshd. Inside tmux or screen that walk finds the multiplexer server instead, so the offer never appears, and the pid file /var/run/release-upgrader-sshd.pid is written only when the extra daemon really starts. Nothing is wrong when you do not see the prompt. You already have the better protection.

If you do accept the offer, the port is not opened for you. The tool says so plainly, because opening a port is a security decision it is not entitled to make on your behalf. Open it for the length of the upgrade, then close it again.

sudo ufw allow 1022/tcp
sudo ufw delete allow 1022/tcp

Most VPS providers run a second firewall in their control panel, outside the operating system. Port 1022 has to be open there as well, or the fallback listener is running and unreachable, which is the worst of both.

Four things belong in place before you type the command:

  • Take a snapshot or a full backup. An in place release upgrade has no undo, and this is the only one you get.
  • Confirm you can open your provider's console before you need it. If the server does not come back after its reboot, SSH is exactly the thing you will not have. A kernel that fails to boot is a separate problem with its own recovery steps, covered in a VPS that will not boot after a kernel update.
  • Check free space with df -h / /boot. The upgrade downloads a full set of packages, and a /boot partition holding several old kernels is a common place to stall.
  • Read the release notes for the services you run. A major version jump in PostgreSQL or PHP arrives with the release, whether or not you planned for it.

FAQ

Why does do-release-upgrade say no new release found on Ubuntu 24.04?

The LTS point release gate is no longer the reason. Until Canonical enabled LTS upgrades on 29 September 2026, about a month after Ubuntu 26.04.1 shipped on 27 August 2026, 26.04 carried Supported: 0 in https://changelogs.ubuntu.com/meta-release-lts, the file the default Prompt=lts reads, so the tool found nothing. Checked on 27 October 2026 that flag is 1, and a 24.04 server is offered 26.04.1. If yours still finds nothing, run sudo do-release-upgrade -c rather than trusting the login banner, confirm the server can reach changelogs.ubuntu.com, and check that Prompt is not set to never. With Prompt=lts the empty answer reads There is no development version of an LTS available., which means the same thing.

Is it safe to set Prompt=normal instead of waiting for the point release?

For 24.04 to 26.04 there is nothing left to wait for. Canonical enabled the upgrade on 29 September 2026, after the point release shipped on 27 August 2026, and checked on 27 October 2026 both meta-release and meta-release-lts mark 26.04 with Supported: 1, so Prompt=lts already offers it and switching gains nothing. Before upgrades were enabled, Prompt=normal upgraded you to the released 26.04 rather than a development build, at the cost of going before the blockers found by early upgraders were fixed. If you switched while you were waiting, set the value back to lts.

Does the -d flag upgrade me to 26.04?

From 24.04, yes. -d takes the first release dated after the one you run, and in both development files that is 26.04, now 26.04.1, which is why Canonical's 26.04.1 announcement tells eager 24.04 users to run do-release-upgrade -d. The newest entry in meta-release-development, checked on 27 October 2026, is Ubuntu 26.10, released on 15 October 2026 but still marked Supported: 0 there and not yet listed in meta-release, and that is where -d points from a 26.04 server. Ubuntu's own server documentation says the development release (or the -d flag) is not recommended for production, and with the LTS gate open a plain do-release-upgrade reaches 26.04.1 without the flag.

apt update returns 404 errors on an old release. How do I upgrade it?

That release has reached end of life, so its packages were moved from archive.ubuntu.com to old-releases.ubuntu.com. Change only the host names in /etc/apt/sources.list.d/ubuntu.sources, or in /etc/apt/sources.list on older layouts, and keep your codename as it is. Then run sudo apt update and sudo apt full-upgrade. Once the system is current again, do-release-upgrade can move it forward one release at a time.

Do I need to remove my PPAs before running do-release-upgrade?

You do not have to, because by default the upgrader comments out third party sources, along with any source that has no Release file for the new release, and logs a line such as was disabled (unknown mirror) for each one. Doing it yourself first is better, since you choose the order and you see the result. Run apt policy on the packages you care about to see which versions each PPA currently offers. APT does not record where an installed copy came from, so treat an installed version that only a PPA offers as a strong hint, and reinstall those packages from the archive if the PPA version is newer than the new release carries.

Was this article useful?