lynxpm update
Aliases: upgrade
๐ Synopsis
Section titled โ๐ Synopsisโlynxpm update|upgrade [flags]Description
Section titled โDescriptionโChecks GitHub Releases for a newer version of Lynx. With --apply, it
downloads and swaps the binary in place โ signature-verified first.
Signature verification: downloaded binaries are checked against an
ed25519 signature (.sig asset) before installation. Releases without a
signature โ or builds where the embedded signing key is empty โ refuse
--apply unless you pass --insecure-skip-signature.
Debian/Ubuntu note: if Lynx was installed from the .deb, prefer
sudo apt install ./lynxpm_*_amd64.deb (or apt upgrade once the
project ships an APT repo). lynxpm update detects the package origin
and refuses --apply unless you pass --force.
โ๏ธ Flags
Section titled โโ๏ธ Flagsโ| Flag | Type | Default | Description |
|---|---|---|---|
-a, --apply | boolean | false | Download, verify, and apply the update if available. |
-c, --check | boolean | true | Check for updates without applying. |
-f, --force | boolean | false | Force update even if managed by the system package manager. |
--insecure-skip-signature | boolean | false | Accept unsigned releases. Dangerous: skips integrity and authenticity verification. |
-h, --help | - | - | Show help message. |
๐ Examples
Section titled โ๐ ExamplesโCheck for updates:
lynxpm updateApply update (requires signed release):
sudo lynxpm update --applyApply update when release is unsigned (not recommended):
sudo lynxpm update --apply --insecure-skip-signatureForce update on a managed system (not recommended):
sudo lynxpm update --apply --force๐ Example Output
Section titled โ๐ Example OutputโUpdate available:
! New version available: v0.7.1 Release notes: https://github.com/Jaro-c/Lynx/releases/tag/v0.7.1
To update, run: lynxpm update --applyAlready up to date:
โ You are using the latest version (v0.7.1)Signature verification failed:
update failed: signature verification failed: ed25519 signature does not match downloaded binarylynxpm listalso surfaces a banner when a newer release is available, backed by a 6-hour cache at$XDG_CACHE_HOME/lynx-pm/update-check.json. So users learn about releases from day-to-day commands without runningupdateexplicitly.