flatpak-update

Update all installed applications and runtimes (use -y to confirm all prompts automatically)

$ flatpak update

$ flatpak update [com.example.app]

$ flatpak update --commit=[COMMIT] [com.example.app]

flatpak update [OPTIONS...] [APPID...]

--all
    Update all installed applications and runtimes. This is the default behavior if no APPIDs are specified.

APPID...
    Specify one or more application IDs to update. If omitted, all applications and runtimes will be updated.

--system
    Update the system-wide installation. This requires root privileges.

--user
    Update the user-specific installation. This is the default if neither --system nor --user are specified.

--no-deps
    Skip updating dependencies. This is generally not recommended.

--no-related
    Skip updating related extensions.

--subsystem=SUBSYSTEM
    Update only a specific subsystem. Valid subsystems include `runtime` and `app`.

--installation=NAME
    Work on a non-default installation.

--appstream
    Only refresh the appstream, no update.

--dry-run
    Simulate the update process without actually making any changes.

--assumeyes
    Automatically answer yes to all prompts.

--noninteractive
    Run non-interactively.

--verbose
    Show verbose output.

--gpg-homedir=PATH
    GPG home directory to use.

--default-gpg-keys
    Use the default GPG keys when verifying signatures.

--ostree-verbose
    Show verbose output from the underlying ostree commands.

The `flatpak update` command updates applications and runtimes installed via Flatpak to their latest available versions. It checks for updates in configured Flatpak remotes, downloads the necessary components, and applies the updates. This command is crucial for keeping your Flatpak applications secure and benefiting from the latest features and bug fixes. It avoids relying on system-level packages by retrieving all the application needs. During the update process, Flatpak ensures that the new versions are compatible with your system and installed applications. If an update requires changes to shared dependencies or runtimes, Flatpak handles these dependencies automatically. The command can also remove obsolete Flatpak components after a succesful update. Flatpak manages the lifecycle of application dependencies, preventing conflicts and ensuring a stable software environment.

Using `--no-deps` can lead to broken applications if dependencies are not met.
System updates usually require root privileges.

0 on success, non-zero on failure.

Flatpak reads its configuration from /etc/flatpak/default.d/*.conf and ~/.config/flatpak/default.d/*.conf.

Unlike system package managers, `flatpak update` is designed to be user-centric. It can safely update user-installed applications without requiring root privileges. Flatpak also isolates applications, reducing the risk of conflicts between different software packages. It also updates the OS level libraries by updating the base runtime.

Flatpak emerged as a solution to address dependency management and application distribution challenges in Linux. It evolved from earlier containerization technologies and gained popularity for its ability to provide a consistent environment for applications across different Linux distributions. The `flatpak update` command is a core part of the Flatpak ecosystem, enabling users to seamlessly update their applications and runtimes without worrying about system-level dependencies. Its development has focused on improving the reliability, security, and user experience of Flatpak application updates. Over time, features like dry-run mode and improved error handling have been added to enhance the command's usability. The command has become vital for maintaining a secure and up-to-date Flatpak application environment.

flatpak install(1), flatpak uninstall(1), flatpak remote-add(1), flatpak list(1)