Deprecated get_source_changelog removed; search gains category/collection filters
v0.72.0
3 featuresThis release3 featuresNew capabilitiesAI-tallied from the release notes
From the original release noteView original ↗
Minor Changes
- 0b1a45e: Remove the deprecated
get_source_changelogtool from the local stdio MCP bridge. It was deprecated in 0.71.0 in favor ofget_catalog_entrywith thechangelog_*params (include_changelog/changelog_path/changelog_offset/changelog_limit/changelog_tokens); callingget_source_changelogby name now returns MCP's standard unknown-tool error. The REST helpersourceChangelog()is unchanged —get_catalog_entryand theadmin source changelogCLI command still use it. - e7d50b4:
releases searchgains--category <slug>and--collection <slug>filters.--categoryscopes hits to organizations in a category (the API validates and resolves curator aliases likee-commerce→commerce, so the value is forwarded as-is);--collectionscopes to a curated collection's member orgs (unknown slugs report "no collection matching …", mirroring--domain). Both forward to the new/v1/searchparams and compose with the existing--domain/--product/--kind/--since/--untilscopes. - 2d4b707: Surface the registry's AI-scored release
importance(1–5,nullwhen unscored).tail/latestgains--min-importance <1-5>(forwarded as?minImportance=); the human table marks importance ≥4 with a quiet glyph (outline at 4, solid at 5), mirroring the web's render threshold, while--jsonoutput (get/tail/latest) passes the raw score through verbatim, includingnull. Bumps the@buildinternet/releases-api-typesand@buildinternet/releases-corepins to the versions that carry theimportancefield.
Fetched July 11, 2026

