npx @buildinternet/releases get releases-shRecently shipped releases publish for non-GitHub CI, source-scoped publish tokens, and a cleanup pass on releases login.
Changelogs publish from any CI, with scoped tokens.
releases publish pushes changelog updates with RELEASES_API_TOKEN from GitLab CI, Buildkite, and local docs builds, using the same plan as the publish-changelog GitHub Action.releases publish-token create/list/revoke mints a relk_ token scoped to one source.releases json validate accepts publish: "push" changelog locators.Login stopped leaving credentials behind. releases login stores only the read-only API key, not a browser session. releases keys and releases publish-token open a one-time approval per run and sign out when it finishes, and each login revokes the relu_ key it replaces. releases auth logout revokes server-side and always clears the local credential.
Agent skills ship with the Claude plugin. The plugin points at agents.releases.sh/mcp, documents which Releases.sh services it reaches and what they keep, and keeps its skills in a self-contained folder that passes Claude plugin validation — npx skills add buildinternet/releases-cli finds them there.
The CLI moved to the buildinternet/releases monorepo. Install commands, GitHub release binaries, and the Homebrew formula are unchanged; releases feedback files issues there. releases list --org <unknown> prints "No sources configured." instead of crashing.
OAuth clients keep their verification controls. create takes --official/--no-official for the "Verified by Releases Index" badge, and update toggles official, trusted, and disabled.
Deprecated: releases admin discovery onboard no longer starts a remote session — the discovery worker and its workflow endpoint were retired. The command exits 1 and points to admin org create, admin source create, and the local-ingest skill.
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.
Atom feed releases now record the date first published instead of last edited, and GitHub-sourced changelogs keep releases collected before a rate limit by treating 403 like 429 to return partial results. Also: sign-in no longer fails on transient KV storage errors, duplicate release URLs return 409 with the conflicting release ID instead of 500, and health probes return a retryable 503 with Retry-After instead of a misleading "run migrations first" message.
Feed validators (ETag / Last-Modified) are now saved only after new releases are stored, so a partial write on one poll no longer causes subsequent polls to skip that content.
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.
When a source republishes the same content under a new title or anchor URL, the duplicate is now dropped and release candidates, backports, and sibling packages are linked as related coverage instead. Bulk-published releases over 20 items now receive AI headlines and summaries, and OAuth discovery documents correctly reflect the authorization code plus PKCE flow.
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.
Source pages for push-fed sources now display the time of the last published update instead of a last-polled time, which doesn't apply to sources updated via the GitHub Action publisher.
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.
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.
GIFs transcoded to MP4 at ingest now render directly instead of being re-encoded a second time, so release pages with animated media load faster.
Published @buildinternet/releases-core@0.35.1 to npm from 5a227591a296fcfea18a08ce93f3d3479c6f7be7.
Bare date filters now include releases through the end of that day across the REST API, MCP tools, and CLI --until flag, and /updates/ day pages, the sitemap, and the digest archive now paginate through the full feed history instead of 404ing or truncating past 100 releases. A duplicate-identity issue blocking some Google sign-ins is cleared and rejected at the database level, and an auth library update closes an OAuth state / magic-link token confusion advisory.
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.