Releases

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.

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.

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.