|FLATPAK UPDATE(1)||flatpak update||FLATPAK UPDATE(1)|
flatpak update [OPTION...] [REF...]
flatpak update [OPTION...] --appstream [REMOTE]
Each REF argument is a full or partial identifier in the flatpak ref format, which looks like "(app|runtime)/ID/ARCH/BRANCH". All elements except ID are optional and can be left out, including the slashes, so most of the time you need only specify ID. Any part left out will be matched against what is installed, and if there are multiple matches an error message will list the alternatives.
By default this looks for both apps and runtimes with the given REF, but you can limit this by using the --app or --runtime option, or by supplying the initial element in the REF.
Normally, this command updates the application to the tip of its branch. But it is possible to check out another commit, with the --commit option.
If the configured remote for a ref being updated has a collection ID configured on it, flatpak will search mounted filesystems such as USB drives as well as Avahi services advertised on the local network for the needed refs, in order to support offline updates. See ostree-find-remotes(1) for more information.
Note that updating a runtime is different from installing a different branch, and runtime updates are expected to keep strict compatibility. If an application update does cause a problem, it is possible to go back to the previous version, with the --commit option.
Unless overridden with the --user, --system or --installation option, this command updates any matching refs in the standard system-wide installation and the per-user one.