Skip to content

v1.6.0 - #63

Merged
vdavez merged 1 commit into
mainfrom
release/v1.6.0
Sep 10, 2026
Merged

v1.6.0#63
vdavez merged 1 commit into
mainfrom
release/v1.6.0

Conversation

@makegov-mark

@makegov-mark makegov-mark Bot commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

Release v1.6.0.

Minor rather than patch: this ships the SLED surface (#62) and the attachments(extracted_text) leaf — new features, not fixes.

  • pyproject.toml, tango/__init__.py and uv.lock bumped together. The first two have to agree, or the published wheel disagrees with the version the package reports about itself.
  • [Unreleased] graduated to ## [1.6.0] - 2026-09-10.

Verified

  • uv build produces tango_python-1.6.0.tar.gz and tango_python-1.6.0-py3-none-any.whl.
  • tango.__version__ and pyproject.toml both read 1.6.0 from the built package.
  • uv run pytest tests/ -m "not integration" — 373 passed, 30 skipped.

Merging this does not publish

publish.yml triggers on release: [published] (or a manual dispatch), not on a push to main. So this PR is safe to merge on its own; creating the v1.6.0 GitHub Release is what ships to PyPI, and PyPI versions are immutable once uploaded.

For reference, main was sitting at 1.5.1 with #62 merged on top — and 1.5.1 is already on PyPI. Cutting a Release before this bump would have tried to re-upload 1.5.1 and been rejected.

🤖 Generated with Claude Code

Minor rather than patch: 1.5.1 → 1.6.0 adds the SLED surface and the `attachments(extracted_text)` leaf, which are new features, not fixes.

Graduates `[Unreleased]`, and bumps `pyproject.toml`, `__version__` and `uv.lock` together — the first two have to agree or the published wheel disagrees with the package it reports itself to be.

Publishing is on `release: [published]`, so merging this changes nothing on PyPI; creating the v1.6.0 Release is what ships it.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@vdavez
vdavez merged commit 7054e84 into main Sep 10, 2026
11 checks passed
@vdavez
vdavez deleted the release/v1.6.0 branch September 10, 2026 15:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant