v0.12.0 #15
AnthonyPuggs
announced in
Announcements
v0.12.0
#15
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Release v0.12.0 is a contract-freeze and release-discipline release for
ausecon-mcp-server.This release does not broaden the server to new sources or new MCP tools. Instead, it stabilises and documents the existing ABS + RBA retrieval surface so downstream clients can rely on it more confidently ahead of
v1.0.0.Highlights
schemas/response.schema.jsonexamples/payloads/metadata.retrieved_atto retrieval responsessrc/ausecon_mcp/filters.pypy.typedfor typed-package consumersWhat Changed
get_abs_data,get_rba_table, andget_economic_seriesnow have a documented, checked-in JSON Schemametadata.retrieved_atin addition to existing provenance fields such asretrieval_url,truncated, andserver_versionlast_n, date windows, and series pruning now lives in one place, reducing the chance of ABS/RBA driftCLAUDE.md, andAGENTS.mdwere refreshed to reflect the frozen retrieval contract and the current preferred discovery surfacesausecon-mcp-serverconsole script is present before publishMCP Surface
There are no new tools in
v0.12.0, and there are no removals.The public MCP surface remains intentionally stable:
search_datasetslist_catalogueget_abs_dataset_structureget_abs_datalist_rba_tablesget_rba_tableget_economic_serieslist_rba_tablesremains in place for backwards compatibility. For new unranked RBA browsing,list_catalogue(source="rba")is now the preferred surface.Breaking Changes
None intended.
This release is designed to be additive and contract-stabilising rather than shape-breaking. In particular, the existing
dimensionspayload shape is unchanged inv0.12.0.Validation
The release work was verified with:
uv run ruff check src testsuv run pytestuv run pytest integration_tests/ -vuv run python scripts/audit_catalogue.pyWhy This Release Matters
Earlier releases focused on correctness, audit governance, and semantic/discovery usability.
v0.12.0is the release that turns the existing retrieval layer into a more explicit public contract.That makes it a better foundation for the final pre-
v1.0.0stabilisation cycle.Notes
As before, the server remains deliberately narrow in scope:
Broader source expansion and transport work remain deferred until after the core contract is stable.
This discussion was created from the release v0.12.0.
Beta Was this translation helpful? Give feedback.
All reactions