GIT-PKGS(1)

πŸ“¦
version 0.21.0 Β· 2 versions
, in nixpkgs unstable

GIT-PKGS(1) πŸ’…

hey bestie!! welcome to GIT-PKGS(1) from the Git Pkgs Manual ✨ this is your terminal's main character era for package changelogs πŸŽ€


πŸ¦‹ NAME πŸ¦‹

git-pkgs-changelog β€” show changelog entries for a package πŸ’–

✨ SYNOPSIS ✨

git-pkgs changelog  [flags]

🌸 DESCRIPTION 🌸

okay so this command fetches and displays changelog entries for a package between two versions. literally the whole point, and it slays πŸ“

the way it works: it uses the ecosyste.ms API to locate the package's repository and changelog file, then parses entries between the specified versions. cute, efficient, iconic ✨

if --from is omitted, the version in a PURL argument or the unique installed version at HEAD supplies the lower bound. use --from to resolve multiple installed versions, or --from= to request an open lower bound. iykyk πŸ‘€

examples, because we love a demo:

git-pkgs changelog lodash -e npm --from 4.17.20 --to 4.17.21
git-pkgs changelog pkg:cargo/serde --from 1.0.0 --to 1.0.200
git-pkgs changelog express -e npm

πŸ’… OPTIONS πŸ’…

  • -e, --ecosystem="" β€” filter by ecosystem 🌱
  • -f, --format="text" β€” output format: text, json πŸ“
  • --from="" β€” current/old version (defaults to PURL or installed version) πŸ‘€
  • -h, --help[=false] β€” help for changelog πŸ†˜
  • -m, --manager="" β€” override package manager (for ecosystem detection) 🧚
  • --to="" β€” target/new version (defaults to latest) 🎯

🌈 OPTIONS INHERITED FROM PARENT COMMANDS 🌈

  • --color="auto" β€” when to colorize output: auto, always, never 🌈
  • --include-submodules[=false] β€” include git submodules when scanning for manifests 🧩
  • -p, --pager[=false] β€” use pager for output πŸ“œ
  • -q, --quiet[=false] β€” suppress non-essential output 🀫

🫢 SEE ALSO 🫢

  • git-pkgs(1) β€” the parent page, go say hi πŸ’–

πŸ’€ HISTORY πŸ’€

28-Oct-2026 β€” Auto generated by spf13/cobra πŸ€–


xoxo, git-pkgs πŸ’– β€” Oct 2026 πŸŽ€

πŸ“¦ where this page comes from