Repository navigation
chore(release): v1.8.0 - #69
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <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
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.
Release v1.8.0.
Minor rather than patch: this ships the Federal Register documents resource, the
alerts.federal_register.matchevent type, theagencyfilter on budget accounts, exclusions and IT Dashboard, and theorganizationexpand on budget accounts, exclusions and SBIR resources (#68). All additive; no existing call changes meaning.pyproject.toml,tango/__init__.pyanduv.lockbumped together.[Unreleased]graduated to## [1.8.0] - 2026-09-28.Verified
uv buildproducestango_python-1.8.0.tar.gzandtango_python-1.8.0-py3-none-any.whl.tango.__version__reads1.8.0.uv run ruff format --check tango/,uv run ruff check tango/anduv run mypy tango/pass (the same scope aslint.yml).uv run pytest tests/ -m "not integration": 430 passed.Merging this does not publish
publish.ymltriggers onrelease: [published](or a manual dispatch), not on a push tomain. Creating thev1.8.0GitHub Release after merge is what ships to PyPI, and PyPI versions are immutable once uploaded.🤖 Generated with Claude Code