chore(release): v1.5.0 - #56
Merged
Merged
Conversation
Minor bump covering the two features that have accumulated on main since v1.4.0, both additive with no breaking SDK surface. `relationships(type, source)` on entities (#54) exposes the two keys the API added to each entity relationship entry, and carries a consumer-facing note worth reading: the `relation` value vocabulary changed upstream, so application code branching on `relation` should match on `type` instead. No SDK code change is required for that — `relation` was and remains a `str`. `PaginatedResponse.meta` (#55) surfaces the API's agency-filter diagnostics, which the SDK previously discarded because it built the response envelope key-by-key. Adds `unresolved_agency_tokens`, `resolved_agencies`, and `agency_warnings`. The second of those is the one that matters for a fuzzy match landing on the wrong organization — nothing is dropped in that case, so a dropped-token check cannot see it. Version bumped in pyproject.toml, tango/__init__.py and uv.lock; [Unreleased] promoted to [1.5.0] - 2026-08-04. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Minor bump to 1.5.0, covering the two features that have accumulated on
mainsince v1.4.0. Both are additive; no breaking SDK surface.4 files changed, 5 insertions(+), 3 deletions(-)— the same shape as the v1.4.0 release (#53): version inpyproject.toml,tango/__init__.pyanduv.lock, and[Unreleased]promoted to[1.5.0] - 2026-08-04.What ships
relationships(type, source)on entities (#54). Exposes the two keys the API added to each entry in the entityrelationshipsexpand.### Changednote before upgrading. Therelationvalue vocabulary changed upstream, so application code branching onrelationshould match ontypeinstead. No SDK code change is required —relationwas and remains astr— but this is the one item in the release that can quietly change a caller's behavior, so it is worth surfacing in the release notes rather than leaving buried in the changelog.PaginatedResponse.meta(#55). Surfaces the API's agency-filter diagnostics, which the SDK previously discarded because it built the response envelope key-by-key. Adds three accessors:unresolved_agency_tokens— tokens that matched no organization, per filterresolved_agencies— the organization each token did matchagency_warnings— the API's human-readable notesresolved_agenciesis the one that matters most and is easiest to undervalue: when a fuzzy match lands on the wrong organization, nothing is dropped, so a dropped-token check cannot detect it. Comparing the resolvednameis the only client-side signal.Also in that PR: a fully-unresolvable agency filter now raises
TangoValidationErrorrather than returning an empty page. That needed no SDK change (the existing 400 handler already reads the API'serrorkey) but it is new behavior forlist_subawards(),list_opportunities(),list_notices()andlist_vehicles().Verification
import tangoreports__version__ == "1.5.0".uv buildproducestango_python-1.5.0sdist + wheel.uv.lockdiff is one line (the project's own version). My localuvinitially rewroterevision = 3→2on regeneration — an artifact of an older local uv, unrelated to this release — so that line was restored rather than shipped.After merge
publish.ymltriggers on GitHub Release published, not on a tag alone. So: tagv1.5.0, then publish the Release to fire the PyPI upload.Once it is on PyPI, makegov/tango-mcp#78's follow-up is unblocked — that repo pins
tango-python>=1.4.0, so the code that would actually surface these diagnostics to agents could not be written until this ships.