@buildinternet/releases-core v0.29.0 internal release
Published @buildinternet/releases-core@0.29.0 to npm from b1a39d30ae3d2ee58e80a702d047c9099053f87d.
Everything shipped on releases.sh — published through our own registry.
Recently shipped release importance scoring, domain ownership claims, and a redesigned /updates timeline.
Release importance scoring (1–5) is now live. All newly ingested releases receive an AI-assigned significance rating. A flame glyph marks high-impact (4) and landmark (5) releases on feed cards and detail pages. GET /v1/releases/latest and the MCP tools get_latest_releases and whats_changed accept a ?minImportance= filter. Importance now reaches collection and category timelines, the following feed, live stream, search results, and related rails.
Domain ownership claims and self-serve listing landed. A new "Own this domain?" panel on listing pages lets signed-in users prove control via a .well-known/releases-verify.txt file or a DNS TXT record; once verified, release tracking activates without curator review. The /submit page validates releases.json manifests and activates listings immediately. The CLI gained releases json export <org> (generates a v2 manifest) and releases json validate <path> (validates against the schema). Unlisted domains that are frequently searched now auto-create stub listings.
Redesigned /updates and homepage. The /updates page now has a timeline rail with month rows and area chips (CLI / Web) for client-side filtering. Composition glyphs show release counts per update. The homepage features an interactive CLI preview with live vitals showing indexed source and release counts. Category and collection scoping for search — GET /v1/search accepts ?category=<slug> and ?collection=<slug>.
Breaking changes are now first-class. The whats_changed MCP tool and GET /v1/whats-changed return changelog entries across a version range with per-release breaking verdicts (none/minor/major) and migration notes. Release cards show a "Breaking" severity badge, and breaking and migrationNotes ride every release read endpoint and search result.
Self-serve webhooks with Slack delivery. Create, list, edit, and delete subscriptions from Account → Notifications or the releases webhook CLI. Set format: "slack" for Block Kit cards. Queue-backed fan-out gives each recipient an independent retry budget.
CLI and API updates. The deprecated get_source_changelog MCP tool was removed — use get_catalog_entry with changelog_* params. releases search now supports --category and --collection filters. releases admin org update gained --auto-generate-content and --overview-cadence flags. Anonymous API reads are served from Cloudflare Workers Cache, and the latest-releases edge cache flushes on publish.
Blume changelogs are now auto-detected. Sites built on the Blume self-hosted Astro changelog generator are ingested via their native RSS feed. Weekly collection digests ship as Markdown, JSON, and Atom — browse past digests and subscribe via API or feed. Release URLs now include human-readable slugs (/release/rel_...-whats-new-in-v2 instead of bare IDs). Org overviews regenerate weekly (was biweekly) and bias toward high-importance releases. Discovery agents use Claude Sonnet 5 for better extraction and search.
Published @buildinternet/releases-core@0.29.0 to npm from b1a39d30ae3d2ee58e80a702d047c9099053f87d.
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.
Published @buildinternet/releases-api-types@0.45.1 to npm from 93617c90db064b5576fa0ad696f4fd5bdedc92bd.
Local stdio MCP bridge's get_catalog_entry tool now accepts changelog parameters to inline a source entry's CHANGELOG in the same call, matching the hosted server. The standalone get_source_changelog tool is deprecated. Also added releases admin release refetch command and consolidated agent skills by moving operator skills to the backend monorepo.
All newly ingested releases now receive an AI-scored significance rating (1–5), with high-impact releases marked by a flame glyph. The /updates page is redesigned with a timeline rail and composition glyphs, and digest emails now bias toward higher-importance releases.
Published @buildinternet/releases-api-types@0.43.0 to npm.
Homepage features an interactive CLI preview with job-led tabs and live vitals strip. Digest emails are redesigned for scannability with grouped org blocks. A new in-place release re-fetch endpoint and auto-materialization for domain lookups are added. Search hits no longer include full markdown by default; pass ?include_content=true to opt in.
Fixed overview stale warning to use content write time (updatedAt) instead of original generation time, so amended overviews no longer appear months-old when recently rewritten.
Published @buildinternet/releases-api-types@0.41.0 to npm from d859f38f12905bdea2cd09294b4e6067e2416a87.
The releases json validate <domain> command now validates live against the registry's listing endpoint and returns the materialization plan (identity, products, release locators with classification). Exit code 0 for valid, 1 for invalid or check failed. Added --url flag to releases admin release update to set or clear a release's canonical URL, and new stub-tier org verbs: create-stub, create-stub-from-domain, and promote with --dry-run support.
Added GET /v1/orgs/:slug/manifest to export tracked orgs as releases.json v2 manifests, and a creating-releases-json Claude Code skill providing agent-guided manifest authoring. The /submit listing check now previews richer details including org identity, per-product source counts, and detected release locations with kind and tier badges.
Published @buildinternet/releases-api-types@0.40.0 to npm.
Domain ownership claims let signed-in users prove control via .well-known/releases-verify.txt or DNS TXT record and enable live release tracking without curator review. Slack notifications now have a dedicated setup guide and UI at /docs/integrations/slack. Fixed a caching bug where auth sessions were served from shared cache, causing signed-in users to appear signed out for up to two hours, and closed a gap where admin and authorization-required API responses could be served to anonymous callers.
Published @buildinternet/releases-api-types@0.39.0 to npm from 71a8a26cc8aa536a0c94afe32c405193992b8102.
Self-serve listing is now available on /submit — enter your domain to validate your releases.json manifest and activate listing immediately, with plain-language previews and field-level error feedback. Changelog pages now render markdown server-side, eliminating shiki and react-markdown from the browser.
Added releases json validate <path> to validate a releases.json v2 owner manifest against the published schema before publishing, with support for file paths, stdin, and machine-readable JSON output. Upgraded to @buildinternet/releases-api-types 0.37.0 and migrated the repo-root releases.json to v2 manifest format.
Organizations known from a releases.json manifest but not yet ingested now appear in the registry catalog with a stub badge, and their declared source locations are surfaced via API and MCP. The org overview citation style was rebuilt to link to release pages on releases.sh instead of inline superscripts, with JSON-LD metadata for SEO; the fenced-JSON citation format is retired.
Removed the releases admin overview batch command whose API route was retired. Added releases admin org update --overview-cadence to pin an org's automated overview-regen cadence (1–90 days) or clear back to the velocity-tiered automatic default; releases admin org get now shows the override when set.
Release URLs now include human-readable slugs (e.g., /release/rel_...-whats-new-in-v2) with permanent redirects from old bare-ID links; the slugged canonical URL flows through MCP tool outputs, Atom feeds, webhooks, Slack cards, and digest emails. A new releases.json v2 manifest at /.well-known/releases.json lets you declare where release notes live and auto-creates sources from feed, github, and appstore locators while reconciling metadata without overwriting curator edits. Also added deep links and "On this page" rail for docs pages, mobile app discovery from Apple's app-site-association file, adaptive org overview refresh rates, and server-side markdown rendering to speed up list pages.
Release cards now display a "Breaking" severity badge on feed cards, org pages, and search results, with a migration notes block added to detail pages when present. The breaking and migrationNotes fields are now returned on all release read API endpoints and search results. releases.sh is now listed on integrations.sh with REST API, MCP server, and CLI declared as integration surfaces.
Added --auto-generate-content / --no-auto-generate-content to releases admin org update, replacing the raw API call previously needed to toggle AI overviews and per-release summaries. Also surfaces current value in releases admin org get and shows an opted_out action in releases admin overview plan for orgs the batch skips.
Discovery agents and search queries now use Claude Sonnet 5 for higher-quality changelog extraction and keyword search. Webhook delivery activity now displays the delivery format (Slack or standard JSON), and new orgs have AI content generation enabled by default.
API and MCP reads are now cached for anonymous traffic on catalog, org, and collection endpoints. Placeholder controls for Bio, Instant release alerts, and Default visibility have been removed from active settings pages.
Sign-in, sign-up, forgot-password, and reset-password pages have been unified with the centered card layout introduced for OAuth and device flows, with consistent typography, button styles, and dark-mode support.
Added user and workspace avatar uploads with editable company website, changelog URL, and GitHub handle fields. Account settings rebuilt with two-pane layout and workspace selector; org pages redesigned with "Copy for agent" split-button, product sparklines, and last-visit dot indicator. Fixed mobile layout on org pages and corrected several account setting copy errors.
The releases webhook add and edit commands now support --format slack to deliver releases as formatted Slack messages via a Slack incoming webhook URL.
Webhook subscriptions now support a slack format option for Block Kit card delivery, and workspaces ship with user invitation, role management, and join/leave controls. Digest email subjects now include the covered date for easier inbox search.
CLI reference docs now document --page-all streaming output, --fields field projection, --input JSON payloads, and --dry-run for write commands. The stale "Summaries & Comparisons" page documenting removed commands has been removed.
Homepage hero stat counts use tabular digits to prevent layout shift, image borders are now neutral instead of tinted, and interactive controls across the site respond with subtle scale-on-press.
Digest email delivery and webhook release fan-out are now queue-backed, giving each recipient an independent retry budget so a transient failure no longer silently drops messages.
New whats_changed MCP tool and GET /v1/whats-changed API endpoint return changelog entries plus per-release breaking-change verdicts (none, minor, major) and migration notes for any package version range. SDK, tool, and platform releases are now classified at ingest for immediate results.
New user-facing releases webhook commands let users manage webhooks directly via CLI, including list, add, show, edit, remove, test, rotate-secret, and deliveries. Patch adds --product, --type, and --clear-* filter flags to webhook add and edit commands for per-event filtering.
Self-serve webhook management now allows creating, listing, updating, and deleting subscriptions with per-event filters and auto-pause on repeated failures. The personalized feed API has switched to cursor pagination, and product/source bylines now omit codename version labels.
New batch release management endpoints — DELETE /v1/releases/batch and POST /v1/releases/batch-suppress — and a rebuilt account settings section with individually-addressable pages. Collection daily summaries now incorporate actual changelog text for SDK version-tag releases.
Digest emails now include real release notes in SDK version-tag rollups, with the most substantive tags rendered as version — one-liner plus a +N more overflow link, while pure dependency-bump entries are ranked out.
New "Get Listed" docs page at releases.sh/docs/listing explains how changelog owners declare their source via releases.json or .well-known/releases.json. Social preview cards now appear on org sub-pages and changelog detail pages, docs and legal pages have correct heading structure, and the JSON Schema URL at releases.sh/schemas/releases.json no longer returns a 404.
Signed-in admin users can now edit orgs, sources, products, and releases inline in production, and view the Status dashboard and fetch logs—previously only available in local dev. The /live feed now shows rich release cards with org identity, descriptive AI titles, and inline media previews.
Collection daily summaries now appear above each day's releases on collection pages, and account settings allow email address changes and social sign-in management. The collection timeline has been rebuilt to group same-product releases, display AI-generated titles, and only show "Show more" when content overflows. Fixed RSS feed parsing for markdown, placeholder display on blank release pages, wrapping for long commands, and an explanation for sign-in forms on incompatible origins.
Passkey sign-in is now available, allowing authentication via Face ID, Touch ID, or a hardware security key. Relative links in ingested release notes now resolve against the vendor's domain, and coverage-side release URLs redirect to the canonical page.
The homepage now features a "What agents ask" section with example prompts, and coverage siblings in the "N other posts cover this launch" rail no longer link to suppressed pages. Homepage refreshes include a "Featured" heading in the org table, compact release counts, and a signup link for signed-out visitors, while status has been removed from the top navigation.
Fixed releases admin source fetch to no longer silently drop a source identifier when combined with --org, matching the behavior of releases latest. Releases import now dedups org accounts on the exact (platform, handle) pair instead of platform alone. Added releases admin source show to inspect a single source's config.
Site-wide notices with configurable colors and optional dismiss buttons are now available, along with avatar facepile previews on category pages and collection search results. Search entity matching has been improved to use word boundaries and relevance ranking, and release detail API responses are now stale for approximately 90 seconds.
Releases.sh now publishes its own product changelog at releases.sh/updates, with daily entries and per-day permalink pages going back to March. The account page now shows when each read-only API key was last used, or marks it as never used.
The release reader ergonomics for get, latest/tail, and list commands have been improved. The README has been trimmed to a leaner npm landing page.
Daily and weekly digest emails are now sent for followed organizations and products, and inline video cards render for Loom, Wistia, Vimeo, and YouTube links. Search results visuals have been clarified, and version-tagged releases now collapse into a per-product rollup.
The CLI now includes verbs to register and manage OAuth clients, including create, list, get, disable, enable, rotate-secret, and delete operations. New verbs also allow for setting, getting, and listing user roles, with options for managing read, curator, and admin privileges.
A personalized feed of organization and product updates is now available, which can be subscribed to via RSS/Atom with a private feed token. Release breadcrumbs now show the organization logo and product name.
Releases is now an OAuth/OIDC provider, enabling other apps and MCP clients to authenticate users through it.
Added releases keys verbs (create/list/revoke) for self-serve, read-only user API keys. These are authenticated via the device-flow session token persisted at login, with transparent re-authentication on expiry.
A new releases login command authenticates the CLI via OAuth 2.0 Device Authorization Grant, storing a read-only API key. The admin org avatar command now allows one-step ingestion of an organization's avatar from a URL, GitHub handle, favicon, or App Store artwork.
Sign in from your browser using device authorization with releases login and create read-only API keys for your account from the web dashboard. The homepage has been refreshed and now features an animated backdrop.
Sign in with Google, including Google One Tap and avatar sync, and magic-link passwordless login are now available.
The CLI now renders curator notices in detail views and JSON output, and added new flags to org, product, and source update commands to set, clear, and link notices. Also added an in-progress banner to admin source fetch-log for managed-agent fetches.
Curators can now post notices on organizations, products, or sources, displayed as banners and pointers in the MCP server. Organization and product pages now include a "Featured in" sidebar. Heavy animated GIFs now play as efficient MP4 video across release pages for faster loading.
Added a --primary flag to admin source create to mark an organization's primary changelog in one step. Also added admin source create-video to materialize a YouTube channel or playlist as a video source.
GitHub star counts now appear on repository-centric pages, and a new public status page with health checks for the service has been added.
The CLI v0.52.0 release introduces several administrative ergonomics, including a new admin source backfill verb that supports dry-runs, keyword allowlists, and atomic metadata settings. It also adds a reextract verb for reprocessing stored release history without live scraping and allows updating featured organizations via the terminal. The backfill command now handles asynchronous dispatch of workflows, returning instance IDs by default.
The search page now includes a timeframe filter to narrow results. Live search is now typing-responsive with no dropped characters or stale results. Videos now show a compact presentation, and the MCP server flags ambiguous bare source or product slugs.
Release images in feeds now open in a redesigned lightbox that keeps the release in context, with left/right paging between every image.
Added App Store source support to the admin CLI with a new releases admin source create-appstore verb and enhanced documentation. The CLI also now surfaces the product’s app-icon avatar.
Browse every tracked organization on a new A-to-Z catalog page, reachable from the header nav. The home page now spotlights featured organizations, and releases on an organization feed can be filtered by time range. Aliased category links now resolve correctly.
YouTube channels and playlists can now be followed as a source for product launches, with releases featuring inline video play. Also added an "Open in [agent]" launcher for one-click setup with Cursor, Claude Code, Codex, or VS Code. Same-day App Store versions and SDK/package releases now roll up or cluster for more compact presentation and easier scanning.
The releases get command now shows products with their latest releases inline and features leaner cards with clearer next steps. The releases search command has gained a --product flag to scope queries to a single product's sources.
Product pages now show their releases directly in the web app and in JSON/markdown formats, with links to Atom feeds. Search can now be scoped to a single product, and MCP server requests for releases get one feed merged across all sources. Fixed a regression where product /changelog URLs landed on a 404.
Product pages are now the default landing and feed unit, with bare /org/product URLs resolving to the product hub. Mobile app releases now render as a compact app-update row. Search results now show the owning product for each release, and owners/curators can rename organizations, products, or source display names from admin menus.
Recommends indexing new changelog sources from the web app and fixes release image rendering, ensuring images previously showing "Image unavailable" now display correctly. Release pages also carry richer structured data and clearer titles for better search-engine and social previews.
Added --max-content-chars [n] to releases admin overview inputs to clip each selected[].content to at most n characters client-side before printing in JSON mode. This prevents silent truncation of long release content in Bash stdout, removing a footgun without requiring a multi-step jq workaround.