Releases

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.

Generic MCP clients (MCPJam and similar) can now complete OAuth against the hosted MCP server — extra grant types are intersected rather than rejected, unrecognized scopes are dropped, and both the origin and /mcp path are accepted as valid resource identifiers. Follow tools that forward the caller's Bearer token to the REST API now work end-to-end.

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.

Hovering a link in a collection digest no longer underlines every link on the page simultaneously, and the current-week digest byline is now visually distinct. Wide docs tables scroll horizontally instead of overflowing onto the TOC rail, and the /docs/api/rest pagination table has been reformatted to fit properly.

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.

Releases ingested through the batch API now have AI-generated titles and summaries before they are indexed for search, instead of embedding without generated content and waiting for a background summarization pass.

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.

Incremental extraction now escalates to a full-page pass when a scrape window returns zero results, preventing silent stalls on sources with long entries. Video sources now trigger site revalidation and route through configured AI models on initial ingest, and the staleness digest no longer re-reports provider outages that have been cleared.

MCP server now implements the 2026-07-28 spec, returning plain JSON to modern clients while maintaining SSE framing for 2025-era clients. The new POST /v1/ai/lanes/:lane endpoint invokes ingest-time AI lanes and can write results back.

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.

Admin status page gains a Health tab that ranks sources by last successful check timestamp, with amber/red alerts for stalled providers. Operator staleness digest now leads with AI provider quota alerts. Backfill dry runs report honest inserted and notStored counts instead of fabricated zeros.

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.