releases
Search and analyze release notes and changelogs from hundreds of products. Releases gives AI agents and coding assistants direct access to u
Open source Repository Open in the app JSON README (API)
About
Search and analyze release notes and changelogs from hundreds of products. Releases gives AI agents and coding assistants direct access to up-to-date product release notes — tracking what's shipping across hundreds of tools, services, and platforms by indexing changelogs, release pages, and support docs from across the web. Releases keeps agents current on what's actually changed. Product teams, engineers, and competitive intelligence analysts use it to monitor their stack, follow integration partners, and spot shifts in their market — without manually checking dozens of release pages.
Details
- Kind
- Plugins
- Topic
- No topic detected
- Publisher
- buildinternet
- Origin
- marketplace
- Category
- ferramentas
- Stars
- 4
- Forks
- 1
- Last push
- 2026-08-30T23:41:34Z
- Repository state
- ativo
- Language
- TypeScript
- License
- MIT
- Added
- 2026-08-30 01:48:58
- Updated
- 2026-08-30 01:48:58
- Origin id
buildinternet/releases-cli/releases
README
# Releases CLI
[](https://www.npmjs.com/package/@buildinternet/releases)
[](https://github.com/buildinternet/releases-cli/actions/workflows/release.yml)
[](https://github.com/buildinternet/releases-cli/actions/workflows/test.yml)
[](./LICENSE)
[](https://github.com/buildinternet/releases)
[](https://skills.sh/buildinternet/releases-cli)
[](https://deepwiki.com/buildinternet/releases-cli)
**[releases.sh](https://releases.sh)** · **[Backend monorepo →](https://github.com/buildinternet/releases)** · [Install](#install) · [Usage](#usage) · [Authentication](#authentication)
The changelog & release-notes registry for developers and AI agents — a lean HTTP client for [releases.sh](https://releases.sh). Search and browse release notes from GitHub, RSS/Atom/JSON feeds, and product changelog pages, with no local infrastructure.
This repo is the **CLI** only. The backend that powers `api.releases.sh` — the API worker, MCP server, web frontend, and ingest pipeline — is open source in its own repo: [buildinternet/releases](https://github.com/buildinternet/releases).
The CLI talks to the hosted registry at `api.releases.sh`. **Search and browse work out of the box — no account or config.** Sign in with `releases login` to follow orgs and products, get a personalized feed, and manage outbound webhooks; it mints a personal **read-only** API key (and earns you higher rate limits as those roll out). Write/admin access (`releases admin …`) is a separate, closed beta — open an issue for early access.
## Install
```bash
brew install buildinternet/tap/releases # Homebrew (macOS / Linux)
npm install -g @buildinternet/releases # npm (macOS / Linux / Windows)
curl -fsSL https://releases.sh/install | bash # shell installer (macOS / Linux)
```
Or run without installing: `npx @buildinternet/releases@latest search react` — always pin `@latest`, since bare `npx @buildinternet/releases` caches the first-fetched version forever. Signed, precompiled binaries for every platform are on the [Releases page](https://github.com/buildinternet/releases-cli/releases) (with checksums) for air-gapped installs or version pinning.
Homebrew installs shell completions automatically. On every other path, enable them once with `releases completion install` (auto-detects `$SHELL`).
## Usage
```bash
releases search "authentication"
releases search "slack integration" --since 90d # bound release hits by publish date
releases tail next-js # latest releases; `tail -f` to follow
releases list --category ai
releases get vercel # org, product, or source
releases org overview vercel # full AI-generated org overview
releases stats
releases submit https://acme.dev/changelog # suggest a source for the registry
releases feedback "great tool — here's an idea…" # message the maintainers
```
Identifiers are interchangeable: every command accepts a slug, a typed ID (`org_…`, `prod_…`, `src_…`, `rel_…`), or an `org/slug` coordinate (e.g. `vercel/next-js`). IDs are stable across renames. `search`, `tail`/`latest`, and `feed` take `--since` / `--until` to bound releases by date — an ISO date (`2026-01-01`) or relative shorthand (`90d`, `4w`, `6m`, `2y`).
Add `--json` to any reader command for machine-readable output — list commands emit a `{ items, pagination }` envelope. Release readers return a slim shape by default (id, version, title, summary, excerpt, url, dates, plus any `media` with its `r2Url`); pass `--full` for the complete payload. `tail`/`latest` take `--count` (alias `--limit`, 1–100). Run `releases <command> --help` for per-command flags.
### Following & personalized feed
Follow orgs and products to build a personalized feed. These act on your own account, so sign in first (`releases login`):
```bash
releases follow vercel # org slug, org/product coordinate, or typed ID
releases following # list what you follow
releases feed # your release timeline (--json, --page, --limit)
releases unfollow vercel
```
Following an organization includes all of its products.
### Outbound webhooks
Receive signed `release.created` POSTs in real time — for everything you follow or a single org:
```bash
releases webhook add --scope follows --url https://your.app/hook
releases webhook add --org vercel --url https://your.app/hook --description "prod"
releases webhook list
releases webhook test <id>
releases webhook verify --key … --signature … --timestamp … --body-file capture.json
```
Org-scoped: up to 10 (`--org`, optional `--source`, `--product`, `--type feature|rollup`). Follows-scoped: one webhook (`--scope follows`) that tracks your current follow graph; optional `--type` narrows delivery. Signing keys are shown once on `add` / `rotate-secret`. You can also manage webhooks in the browser at [releases.sh/account/notifications](https://releases.sh/account/notifications). Operator/admin webhooks (`releases admin webhook …`) are a separate root-key surface.
### Contribute to the registry
None of these need an account or API key:
```bash
releases submit https://acme.dev/changelog # suggest a changelog / release-notes URL
releases feedback "tail -f reconnects slowly" # report a bug or share an idea
releases json validate releases.json # check a releases.json manifest before publishing
```
`submit` and `feedback` both prompt interactively when run with no argument, accept input on stdin, and take `--dry-run --json` to preview the payload without sending. `feedback --type` is `bug` / `idea` / `other`; `submit --note` carries extra context (product name, repo, feed quirks). Submissions feed the same review queue as the [web submit form](https://releases.sh/submit).
`json validate` is a read-only manifest check: it validates a [`releases.json`](https://releases.sh/docs/listing) v2 file against the published schema (pass a path or `-` for stdin) and adds `--json` for machine-readable output — no network, no submission.
### MCP & Claude Code
Point any MCP-compatible agent at the hosted server:
```bash
npx mcp-remote https://mcp.releases.sh/mcp
```
This repo is also a Claude Code marketplace with the `releases` plugin — hosted MCP tools, a `/releases` lookup command, and auto-trigger skills:
```bash
/plugin marketplace add buildinternet/releases-cli
/plugin install releases@releases
```
Operator/maintainer skills (source onboarding, parsing, playbooks) live with the backend in the [releases monorepo](https://github.com/buildinternet/releases) — its `.claude/skills/` tree is picked up automatically in a checkout.
Or install just the skills into any agent (Cursor, Codex, Gemini CLI, Windsurf, …):
```bash
releases skills install # or, without the CLI: npx skills add buildinternet/releases-cli
```
## Authentication
Search and browse need no auth. Signing in powers the personal surfaces — **follows, feed, and outbound webhooks** — and mints a personal **read-only** key (it can't write to the catalog or run `admin` commands; it identifies you for `/v1/me/*` account routes). The easiest way in is your browser — nothing to copy or paste:
```bash
releases login # opens your browser to approve, then saves the key
releases login --no-browser # print the URL + code to open yourself (headless / SSH)
```
This uses the OAuth 2.0 Device Authorization Grant (RFC 8628): approve a short code at [releases.sh/device](https://releases.sh/device) in a signed-in browser, and a read-only key is saved to `~/.releases/credentials` (`0600`). Manage keys with `releases keys list` / `create` / `revoke`.
Already issued a token (e.g. a write/admin key during the closed beta)? Store it without the browser flow via `releases auth login` (interactive, `--token <token>`, or `--token -` for stdin); it's verified before being saved. `releases auth status` shows the current state (`whoami` is an alias). `RELEASES_API_KEY` in the environment overrides any stored credential — handy for CI.
## Environment
Reader access requires nothing. Useful overrides:
- `RELEASES_API_KEY` — Bearer token for write endpoints; overrides stored credentials.
- `RELEASES_API_URL` — override the default `https://api.releases.sh` (e.g. staging).
- `RELEASES_TELEMETRY_DISABLED=1` — opt out of anonymous usage pings (`DO_NOT_TRACK=1` also honored).
See [`.env.example`](./.env.example) for the full list.
### Custom CA certificates (TLS-intercepting proxies)
The compiled binary ships with the standard Mozilla CA store. If your network re-terminates TLS with its own CA (corporate proxy, sandboxed agent environment), point the standard Node/OpenSSL variables at the proxy's CA certificate — the binary honors both:
```sh
NODE_EXTRA_CA_CERTS=/path/to/proxy-ca.pem releases search "bun"
# or
SSL_CERT_FILE=/path/to/proxy-ca.pem releases search "bun"
```
No `--ca-bundle` flag is needed; certificate errors from the CLI include this hint.
## Exit codes
| Code | Meaning |
| ----- | ------------------------------------------------------------ |
| `0` | Success |
| `1` | Application error (network, API, unexpected state) |
| `2` | Usage / provider error (bad arguments or upstream rejection) |
| `130` | Cancellation (SIGINT) |
## Contributing
Build, test, and release instructions live in [CONTRIBUTING.md](CONTRIBUTING.md).
## License
MIT