Everything shipped on Release Notes Index — published through our own registry.
Recently moved the CLI's public API calls onto @buildinternet/releases-sdk and added the filters search and list commands had been sending all along.
The CLI runs on the shared SDK. Follows, the feed, webhooks, workspaces, release reads, collections, search, domain lookup, changelogs and overviews all route through the SDK. Org, product and source lookups and releases publish use it too.
releases feed changed its paging flag. --page is gone — the API rejects it — so scripts need --cursor instead.
Search and org filters now land.
releases search --org <slug|org_…> filters by organization and echoes org / orgStatus in results.platform; an org's release feed filters by minImportance.SearchQuery, OrgListQuery and OrgReleasesQuery take all three, and api-types carries the search fields.Changelogs push from any CI. releases publish sends changelog updates with RELEASES_API_TOKEN from GitLab CI, Buildkite and local docs builds, using the publish-changelog plan; releases json validate accepts publish: "push" locators. Publish tokens are scoped to a single source.
Smaller. Compiled binaries build with Bun 1.4.4, which drops the compromised eMudhra intermediate certificates (CVE-2026-111943). Install commands, GitHub release binaries and the Homebrew formula point at the buildinternet/releases monorepo; releases feedback files issues there.
Public API calls now route through @buildinternet/releases-sdk, and releases feed pages with --cursor instead of --page, which the API rejects. Org, product and source lookups plus releases publish also moved to the SDK, surfacing real Created/Updated times in org get, fetch priority in source show, and replacing org list's always-empty Updated column with the last release date.
Published @buildinternet/releases-api-types@0.60.0 to npm from 8d9bde8214272f4755f9297a89f79ac89ed6e92a.
Published @buildinternet/releases-core@0.35.3 to npm from 764ca21be2f6508003bbb8c1df2c36e56ccda272.
A new @buildinternet/releases-sdk npm package calls the public API from Node, Deno, or any bundler, and releases-core plus releases-api-types now ship as compiled ES modules. The releases feed CLI paginates with --cursor instead of --page, which the API always rejected with a 400, and org and source commands now display real timestamps and fetch priority instead of "—".
Compiled CLI binaries are now built with Bun 1.4.4, which no longer trusts the compromised eMudhra intermediate certificates tracked as CVE-2026-111943.
Published @buildinternet/releases-api-types@0.59.0 to npm from 96aba0dbcb4c2b83e73773e5583db4c8518a42ee.
Added a pricing page at /pricing covering the free tier, how a free account raises the API rate limit, and which personal features require sign-in, also available as /pricing.md. Static pages now serve Markdown via Accept: text/markdown or the .md URL with a link rel="alternate" tag in the head, fixing a "View .md" button that pointed to a nonexistent path.
Published @buildinternet/releases-core@0.35.2 to npm from 2246048b7c771f6e5a27d30d46d92caf41b888be.
Selected source histories — Anthropic Claude Code, OpenAI, xAI, Cloudflare, and Vercel changelogs — are now published as indexed dataset pages with descriptions, making them discoverable in search engines. MCP release results now put the original source URL first, and release cards link directly to the upstream post when one is available.
Published @buildinternet/releases-api-types@0.58.3 to npm from c137bfe82bd8df6a82b7156d786e6e2125b21cb3.
Verified domain owners can copy a Markdown or HTML snippet to add a Release Notes Index badge linking to their org page, and /release/<id>.json now returns application/json instead of Markdown. Pages also gained Markdown alternate links in the head, and /google-gemini URLs now redirect permanently to /google.
releases feedback now opens issues on buildinternet/releases, where the CLI lives.
releases list --org <unknown> and --product <unknown> now print "No sources configured." instead of crashing with a pageItems.length error, because the sources client normalizes bare-array responses from older API deploys. The CLI is also now built and published from the buildinternet/releases monorepo, with install commands unchanged.
Published @buildinternet/releases-api-types@0.58.2 to npm from 22b9c4273f74bdffc0e063c2573a4601ddc02ae3.
Collections now email a weekly summary to subscribers, with past digests replayable on the web, and collection, digest, source changelog, and updates pages refresh automatically when new releases land. GitHub tag filters now apply in production, and fixes cover AVIF/MP4 thumbnails, a releases list crash on unknown org slugs, and 404ing relative links in the CHANGELOG viewer.
Published @buildinternet/releases-core@0.35.1 to npm from 5a227591a296fcfea18a08ce93f3d3479c6f7be7.
New releases publish command lets GitLab CI, Buildkite, and local docs builds push changelog updates with RELEASES_API_TOKEN, reusing the plan from the publish-changelog GitHub Action. releases json validate now accepts publish: "push" changelog locators from the current releases.json schema.
Published @buildinternet/releases-core@0.35.0 to npm from eb0a9d3eca94a0c2b0004d232c657309c6f46a95.
The product name is now consistently "Release Notes Index" across sign-in screens, social preview images, the MCP server's display name in connected clients, and in-product copy.
Adds --official / --no-official to releases admin oauth client create and a new releases admin oauth client update command for the official, trusted, and disabled flags, with official now shown in client list and get output. The flag controls the Verified by Releases Index badge and requires an API with buildinternet/releases#2421; older APIs ignore official on create and reject an update that sets only official.
releases.json now supports declaring a GitHub Action-fed changelog in the domain manifest with "publish": "push" alongside the github and path fields; the listing flow returns the domain-verify, token-mint, and Action-wire-up steps automatically, with no separate manual source setup.
Connecting Claude to the MCP server using its published identity now registers automatically by fetching Claude's client metadata on first connect, with no manual pre-registration step. The OAuth consent screen now lists follows and webhooks to match the granted permissions, and dark mode no longer flashes light on first load because the theme bootstrap runs as an inline head script.
Agent skills now live in the self-contained Claude plugin folder at plugins/claude/releases/skills/ so the plugin passes Claude plugin directory validation, with npx skills add buildinternet/releases-cli finding them at the new path and the skills update check reading it. The Claude plugin also points at the agents.releases.sh/mcp endpoint, with documentation, support and terms links added to its manifest.
releases login now persists only the read-only API key it mints, and releases keys and releases publish-token open a fresh one-time browser approval per command that is signed out when the command finishes; every subcommand accepts --no-browser to print the URL and code instead. releases auth logout revokes the stored key directly and always removes the local credential, and pre-existing credential files are upgraded in place by signing out and stripping any leftover session token.
Published @buildinternet/releases-core@0.34.0 to npm from 5ab8cbd3505a6975853b9dc3fa3e11d40f41ff20.
Verified domain owners can mint per-source publish tokens from Account → Webhooks & API, with mint and revoke commands available in the CLI, and set changelog-glob in publish-changelog to publish one-file-per-entry Markdown or MDX changelogs with frontmatter metadata. An "Own this domain?" link now lets owners claim any tracked org, CLI approval screens are distinct per command with releases login no longer keeping a long-lived session, and the per-user read-only API key cap rises from 5 to 25.
Published @buildinternet/releases-api-types@0.55.0 to npm from f75a41738a82c3935dfc8e8181fdbed3d0f60f03.
releases admin discovery onboard no longer starts a remote discovery session, as the discovery worker and POST /v1/workflows/discover were retired; the command now exits 1 with a pointer to releases admin org create, releases admin source create, and the local-ingest skill. The onboard apply subcommand and the --managed-agents and --sandbox engine flags are removed.
New GET /v1/collections/:slug/digests/latest returns the current week's digest without knowing the week date, and the collection page now loads it in parallel with the feed. MCP tools follow the REST API's visibility rules so deleted and hidden orgs, products, and sources no longer appear in lookups, search, the org directory, latest releases, or tab completion; weekly digest summaries now group a product's multiple updates into one account.
Published @buildinternet/releases-api-types@0.53.0 to npm from c4bcf47ed731cd72964d03814395d7869909ae4c.
Interest alerts let you describe what you care about in plain language and get notified by email or webhook when a release you already follow matches, with a default confidence of 0.80 and up to five interests. Also added workspace webhooks for teams, MCP tools for managing personal and workspace webhooks, and weekly digest reels on collection pages.
Published @buildinternet/releases-api-types@0.52.1 to npm from afaa39a228aa28d2d677e8dce0bb3afd3cfc094b.
Published @buildinternet/releases-api-types@0.52.0 to npm from 2e9afb6cbd60b58b951f013fa622b8789a5ae482.
A new publish-changelog GitHub Action diffs a changelog file on each push, maps changed sections onto upserted releases, and posts them to your Releases Index source, with re-running the same commit a no-op. Fixed sources that silently stopped polling now self-heal on manual fetch, re-enable, or the hourly heartbeat, and release cards reject CDN thumbnails where both dimensions are 128 px or smaller.
releases webhook add and edit now accept --format discord to deliver releases as formatted Discord embeds via a Discord incoming webhook URL. Human-readable webhook output redacts the delivery URL, while --json still includes it.
New releases admin recommendations notify-added command lets operators opt in to emailing a submitter that their suggested source was added to the registry.
Webhooks can now target a Discord incoming webhook URL and deliver release.created events as native Discord embeds alongside Slack and signed JSON, and workspace owners and admins can link an uploads.sh account under Account → Integrations. Header search now opens a typeahead in place instead of navigating away on the first keystroke.
The product's primary name is now "Release Notes Index" across the homepage hero, header wordmark, OG metadata, and llms.txt, with "Releases Index" in page titles, footer, and emails; domain, API paths, and the CLI binary are unchanged. The MCP server's primary URL is now https://agents.releases.sh/mcp, with https://mcp.releases.sh/mcp remaining a working alias for existing tokens and client configs.
New releases changelog command prints recent product updates from releases.sh and links to https://releases.sh/updates. The same capability is exposed as the local MCP changelog tool.
MCP clients can now complete OAuth authorization — resource-request validation and a column encoding bug were blocking scope grants — and sessions issue refresh tokens so clients stay connected past the one-hour expiry. The docs site adds how-to guides for locating changelog sources, converting changelogs to RSS/Atom feeds, and setting up release notifications.
OpenAPI spec now registers the error envelope as a named ErrorEnvelope component, replacing anonymous inline definitions so code generators and API tooling can reference the shape directly. Nonexistent API and docs paths return a text/markdown 404 body with pointers to llms.txt, the docs index, the REST API base, and the OpenAPI spec, and llms.txt gains a "When to use" section.
Unified feedback, submit, and keys command network calls onto the shared apiFetch transport, adding an opt-in skipDefaultAuth flag so keys' session-token Authorization header isn't overwritten by a configured admin/API key. Error messages, idempotency, and command output are unchanged.
Published @buildinternet/releases-api-types@0.51.0 to npm from 5ffcb358dc397383ad05b325e8fc0db997169755.
API writes now support Idempotency-Key headers for token, API key, and webhook operations, returning the same response on retries within 24 hours. Rate limit errors use the standard structured error envelope with Retry-After and policy headers.
Search timeframe filters open as a popover on the search bar, reused across org, source, and collection timeline views. Webhook settings use proper selects, and destructive actions open a confirmation dialog instead of a browser prompt.
Release title links across org and product pages, the homepage ticker, /updates, live stream, following, collection timelines, and digest emails now go directly to the upstream changelog entry. The on-site release detail page remains accessible via a secondary "Read more" or "Details" link on each card.
Verified owners now receive a confirmation email when their domain claim is accepted, and the claim panel shows promotion eligibility. Fixed CORS gaps breaking sign-in, domain claim, and listing promote flows, and broken media thumbnails now hide cleanly across the feed.
New releases now appear on the site sooner because page revalidation is triggered at ingest time instead of on a background schedule. Incremental extraction escalates to a full-page pass when a scrape window returns zero results on a changed page, and video sources now trigger revalidation and route through configured AI models on initial ingest.
The MCP server now implements MCP spec 2026-07-28, so modern clients receive plain JSON responses while 2025-era clients continue receiving SSE framing unchanged.
getApiUrl() no longer memoizes the API base URL process-wide, fixing a test isolation bug that caused 22 failing tests under bun test. The releases stats command now reads the server's real values instead of returning zeroed-out fields, and source backfill --dry-run reports how much history is not yet stored.
Published @buildinternet/releases-api-types@0.50.0 to npm from 239cc6dc8f29cd74c42ed78a79bcf4a674954f87.
Digest, magic link, password reset, verification, and operator alert emails now use a unified branded shell, and digest emails render markdown in release bodies instead of raw asterisks. Email subject lines now include more context — leading orgs in digests, expiry times in magic links and password resets, and source or org names in operator alerts.
Published @buildinternet/releases-core@0.29.0 to npm from b1a39d30ae3d2ee58e80a702d047c9099053f87d.
App Store release cards in related rails and the homepage ticker now display as compact entries with only app icon, name, iOS/macOS label, and date. Routine App Store updates are filtered from cross-product discovery surfaces unless the release carries an AI importance score of 4 or higher.
Org pages now open on the Releases feed, with Overview moved to /:org/overview and /:org/releases redirecting to the org root. Copy buttons on /docs code blocks are always visible, and text blocks soft-wrap instead of scrolling horizontally.
Org overviews now prioritize releases with importance ≥ 4, preventing landmark updates from being buried by routine churn. Site footer reorganized with a new Collections column, Webhooks moved under Docs, and an uploads.sh cross-link added.
Search results now include an AI-scored importance field (1–5) in JSON output, with the TTY table marking high-importance hits. Added a TLS certificate verification hint and custom-CA documentation for proxy environments.
Published @buildinternet/releases-api-types@0.48.0 to npm.
Blume self-hosted Astro changelog sites are now auto-detected and ingested via RSS feed. Collection weekly digests are available in Markdown, JSON, and Atom formats, with recent digests surfaced in the collection right rail. AI-scored importance now reaches feeds, search, and MCP results.
Site wordmark, entity page titles, and social-share OG images now render in the Geist Pixel font.
Published @buildinternet/releases-api-types@0.47.0 to npm from eb15f11d506c683f69a813848d320b8425b230d2.
Weekly collection digests now available, with AI-written summaries published at /collections/[slug]/digest/[week] and exposed via REST API. Release sitemap at /v1/sitemap/releases surfaces importance-gated releases for search engine indexing. Release pages show a labeled divider between AI summary and original note.
Removed the deprecated get_source_changelog MCP tool, replaced by get_catalog_entry with changelog params. Search now supports --category and --collection filters, and the release importance score is surfaced in tail/latest output.