Loading search…

Explain with AI
Edit this page

Version and Updates

Last updated

Show the installed version and update comic-dl through the tool that installed it — package manager, pip, uv, or a source checkout.

On this page

comic-dl self inspects how comic-dl is installed and updates it through the tool that owns that installation. It never guesses and never downgrades.

Show the installed version

comic-dl self version

Update

comic-dl self update [--check] [-y] [--channel beta]

self update asks the GitHub Releases API for the latest published version and reports the installation source, installed version, latest version, and status:

Installed via:        uv tool
Installed version:    0.0.2
Latest version:       0.0.3
Status:               update available.
  • --check only checks; nothing is installed or changed.
  • -y / --yes skips the confirmation prompt. Without a TTY and without --yes, the update refuses rather than proceeding unattended.
  • --channel selects the release channel. Only beta exists today; stable ships once the release pipeline formalizes it.

What happens, by installation type

Installation What self update does
Debian/Ubuntu (apt) Downloads the .deb for your architecture, then runs sudo apt install after you confirm the sudo prompt
Fedora/RHEL (dnf) Downloads the .rpm, then sudo dnf install
Arch (pacman) Downloads the .pkg.tar.zst, then sudo pacman -U
pip environment Runs python -m pip install --upgrade comic-dl — only when the environment is writable
uv tool Runs uv tool upgrade comic-dl
Source checkout Prints git pull and uv sync; never modifies the checkout
Standalone executable Prints where to download the new release; does not replace itself yet
Unknown Reports that it cannot identify the installation and points at the releases page

If you decline the confirmation (or an install fails), comic-dl prints the exact command to run yourself. If the network or the GitHub API is unavailable, the check reports that and leaves everything unchanged — a failed update check never affects normal downloads.

Downloads are made over HTTPS through the same SSRF-validated, rate-limited fetch path as scraping, and package installs run through the owning package manager (which verifies package signatures). Only visible package defaults are used; comic-dl never adds flags like --user or --break-system-packages.