releases

Releases CLI

The changelog & release-notes registry for developers and AI agents. A lean HTTP client for releases.sh — search and browse release notes from GitHub, RSS/Atom/JSON feeds, and product changelog pages without any local infrastructure.

The CLI talks to the hosted registry at api.releases.sh. Reader commands work out of the box with no configuration.

Admin access is currently closed beta. releases admin … commands require an API key, and API keys are not self-serve yet — the hosted registry doesn't expose a public signup flow for them. If you'd like early access, open an issue and we'll get in touch. Everything below the install section assumes reader-only use unless stated otherwise.

Install

Homebrew (macOS / Linux)

brew install buildinternet/tap/releases

npm (macOS, Linux, Windows)

npm install -g @buildinternet/releases

Or run without installing:

npx @buildinternet/releases@latest search "react"

Always include the @latest tag — bare npx @buildinternet/releases caches the first-fetched version forever and won't pick up updates.

Shell installer (macOS, Linux)

curl -fsSL https://releases.sh/install | bash

Downloads the matching platform binary from npm. Respects RELEASES_INSTALL_DIR (default: /usr/local/bin). Windows users should use npm or the GitHub Releases archive below.

Precompiled binaries (GitHub Releases)

Every version publishes signed archives for each platform on the Releases page — releases-{darwin-arm64,darwin-x64,linux-arm64,linux-x64}.gz and releases-windows-x64.zip, each with a matching .sha256 and a top-level checksums.txt. Useful for air-gapped installs, version pinning, or platforms where npm and Homebrew aren't an option.

Shell completion

Homebrew installs bash, zsh, and fish completions automatically — nothing extra to do. For every other install path (npm, the curl | bash installer, and the raw GitHub binaries), enable completions once:

releases completion install          # auto-detects $SHELL
releases completion install zsh      # or pick explicitly

install writes to the conventional location (~/.zsh/completions/_releases, ~/.local/share/bash-completion/completions/releases, or ~/.config/fish/completions/releases.fish) and prints any rc-file lines you may need to add. The bash and fish paths honor $XDG_DATA_HOME and $XDG_CONFIG_HOME respectively, so the file lands wherever those point if set. Pass --path <file> to override the destination. To pipe the script somewhere yourself:

releases completion zsh > /path/to/_releases

On an interactive terminal, a persistent, self-resolving notice on the landing screen and --help reminds you to run this until shell completion is detected — and stops on its own once completions are set up (including the automatic Homebrew install). Set RELEASES_NO_COMPLETION_HINT=1 to silence it.

Usage

releases search "authentication"
releases search "slack integration" --since 90d   # filter release hits by publish date
releases tail next-js                    # or `releases tail -f` to follow new releases
releases tail src_abc123                 # IDs work everywhere a slug does
releases tail --since 30d                # only releases from the last 30 days
releases list --category ai
releases get vercel                      # org, product, or source
releases get org_abc123                  # typed IDs are accepted
releases org overview vercel             # full AI-generated overview for an org
releases stats
releases feedback "great tool, here's an idea…"   # send feedback to the maintainers

Every command that takes an org / product / source / release identifier accepts the typed ID form (org_…, prod_…, src_…, rel_…) interchangeably with the slug. IDs are stable across renames; slugs are friendlier when typing. Sources and products also accept the org/slug coordinate form (e.g. vercel/next-js).