Skip to content

release: 1.3.1 — waiting turns keep their order in the receive loop - #20

Merged
sanctrl merged 2 commits into
mainfrom
release/1.3.1
Nov 11, 2026
Merged

sanctrl merged 2 commits into
mainfrom
release/1.3.1

Conversation

@sanctrl

@sanctrl sanctrl commented Nov 11, 2026 •

Copy link
Copy Markdown
Contributor

Why

The founder approved releasing the Python SDK as 1.3.1. It carries the receive-loop fix from #19: a turn gated while a freed slot was being handed on could start ahead of the turns already waiting for that slot. Now waiting turns go first, in order.

Separately, VERSIONING.md said the first slot is "frozen at 0". This package has been 1.x on PyPI since 1.0.0 (May 2026), and a registry never takes a number back.

What changes

  • Version 1.3.1 in pyproject.toml and src/agentchatme/_version.py. These are the two files publish.yml's verify step compares with the tag.

  • CHANGELOG: the Unreleased section becomes 1.3.1 — 2026-11-11.

  • VERSIONING.md states the rule as applied here:

    • the first slot stays 1 and is never bumped;
    • minor +1 for rebuilt or added behaviour, patch +1 for fixes;
    • always +1, never append digits;
    • the founder sets every number.

    Since the first slot never moves, it also says that a change which would break existing callers has no slot under this rule, and is the founder's decision.

  • The CHANGELOG preface and the README's Versioning section said "breaking changes bump the major", which contradicts that rule. Both now point at VERSIONING.md, by absolute URL, because the sdist ships CHANGELOG.md but not VERSIONING.md.

Proof

  • ruff and mypy are clean. pytest on 3.9, 3.10, 3.11, 3.12 and 3.13: 718 passed and 2 skipped on each.
  • The contract-fixture check matches the live manifest.
  • uv build: agentchatme-1.3.1-py3-none-any.whl and agentchatme-1.3.1.tar.gz. The metadata has Version: 1.3.1 and Documentation: https://docs.agentchat.me/sdks/python.
  • publish.yml's verify logic, run locally: tag v1.3.1 passes, and v1.3.0 is refused.
  • Independent review: no bugs found. Fixed from it: the README changes in the notes, the absolute link, and dropping a compatibility promise the rule doesn't make.

Test plan

  • CI green on the head commit: check on ubuntu, macOS and Windows × 3.9 / 3.11 / 3.13, plus secret-scan (run 43004413469)
  • after merge: tag v1.3.1 on the merge commit; publish.yml verify, test and build pass, then the pypi environment approval
  • PyPI shows 1.3.1 with the new Documentation link

- Version 1.3.1 in pyproject.toml and src/agentchatme/_version.py (the
  two files publish.yml's verify step compares with the tag).
- CHANGELOG: the Unreleased section becomes 1.3.1 — 2026-11-11, with the
  docs that ship in the package since 1.3.0 (docstrings, the PyPI
  Documentation link, the README samples).
- VERSIONING.md said the first slot is frozen at 0; this package has been
  1.x on PyPI since 1.0.0 and a registry never takes a number back. It now
  states the rule as applied here: the first slot stays 1, minor +1 for
  rebuilt or added behaviour, patch +1 for fixes, existing callers keep
  working (a renamed name ships next to the old one), the founder sets
  every number.
- The CHANGELOG preface and the README's Versioning section said breaking
  changes bump the major, which contradicts that rule; both now point at
  VERSIONING.md.
…G link, no new policy line

- CHANGELOG 1.3.1 Docs: the README entry now names everything that ships
  as the PyPI description: the text= and type="file" samples, CallOptions,
  the rewake note, and the Links section.
- The CHANGELOG preface links VERSIONING.md by absolute URL: the sdist
  ships CHANGELOG.md but not VERSIONING.md.
- VERSIONING.md no longer adds a compatibility promise of its own; it says
  a change that would break existing callers has no slot under this rule
  and is the founder's decision.
@sanctrl
sanctrl merged commit e6eeb2c into main Nov 11, 2026
11 checks passed
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