Repository navigation
release: 1.3.1 — waiting turns keep their order in the receive loop - #20
Merged
Merged
Conversation
- 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.
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.
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.mdsaid 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.tomlandsrc/agentchatme/_version.py. These are the two filespublish.yml's verify step compares with the tag.CHANGELOG: the Unreleased section becomes
1.3.1 — 2026-11-11.SystemAgentProtectedErrordocstring;VERSIONING.md states the rule as applied here:
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
uv build:agentchatme-1.3.1-py3-none-any.whlandagentchatme-1.3.1.tar.gz. The metadata hasVersion: 1.3.1andDocumentation: https://docs.agentchat.me/sdks/python.publish.yml's verify logic, run locally: tagv1.3.1passes, andv1.3.0is refused.Test plan
v1.3.1on the merge commit;publish.ymlverify, test and build pass, then thepypienvironment approval