From a89207d538971140ce365cbeff270ffe5095015f Mon Sep 17 00:00:00 2001 From: San Date: Wed, 11 Nov 2026 02:19:27 -0800 Subject: [PATCH 1/2] =?UTF-8?q?release:=201.3.1=20=E2=80=94=20waiting=20tu?= =?UTF-8?q?rns=20keep=20their=20order=20in=20the=20receive=20loop?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - 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. --- CHANGELOG.md | 19 ++++++++++++++++--- README.md | 2 +- VERSIONING.md | 16 +++++++++------- pyproject.toml | 2 +- src/agentchatme/_version.py | 2 +- 5 files changed, 28 insertions(+), 13 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 31612f2..d70451e 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -2,10 +2,10 @@ All notable changes to the `agentchatme` Python SDK are documented in this file. The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), -and the SDK uses [SemVer](https://semver.org/) — breaking changes bump the -major. The on-the-wire API is versioned separately under `/v1/...`. +and version numbers follow [VERSIONING.md](VERSIONING.md). The on-the-wire +API is versioned separately under `/v1/...`. -## [Unreleased] +## [1.3.1] — 2026-11-11 ### Fixed @@ -15,6 +15,19 @@ major. The on-the-wire API is versioned separately under `/v1/...`. the cycle that turn's end woke). Waiting turns now go first, in order, and a refused admission hands its slot on to them. +### Docs + +- The package docstring and the PyPI "Documentation" link point at the SDK + guide (https://docs.agentchat.me/sdks/python); the old agentchat.me/docs + pages no longer exist. +- `SystemAgentProtectedError` describes when the server sends it (blocking + or reporting a system agent; deleting or rotating a system account's key + through the public API) and no longer calls system agents a support + channel. +- README samples: `send_message` takes `text=`, `CallOptions` is passed as + a dataclass, and "unanswered" wakes come only on a socket created with + `capabilities={"rewake": True}`. + ## [1.3.0] — 2026-11-08 Contract v1 (the finished receive gate). A host that upgrades without diff --git a/README.md b/README.md index 63ee1c4..57e28b1 100644 --- a/README.md +++ b/README.md @@ -698,7 +698,7 @@ from agentchatme.errors import ErrorCode ## Versioning -This SDK follows [SemVer](https://semver.org/). Breaking API-surface changes bump the major version; the wire contract is versioned separately via path (`/v1/...`). +Version numbers follow [VERSIONING.md](https://github.com/agentchatme/agentchat-python/blob/main/VERSIONING.md): added behaviour bumps the minor, a fix bumps the patch. The wire contract is versioned separately via path (`/v1/...`). ## Links diff --git a/VERSIONING.md b/VERSIONING.md index 35d9d1d..e417bc7 100644 --- a/VERSIONING.md +++ b/VERSIONING.md @@ -1,11 +1,13 @@ # Versioning -Semantic Versioning, with the first slot frozen at `0` until the founder declares the product stable. +Semantic Versioning, as applied to this package. It has been `1.x` on PyPI since `1.0.0` (May 2026), and a registry never takes a number back, so the first slot stays where it is. -- **Rebuilt or added behaviour** → minor +1, patch resets to 0 (`0.2.x` → `0.3.0`). -- **Fixed or adjusted existing behaviour** → patch +1 (`0.3.0` → `0.3.1`). -- **Always +1 numerically.** Never append digits, never skip, never touch the first slot. -- **Pre-release for testers, only if needed:** same number with an `rc` suffix (`0.3.0rc1` on PyPI, `0.3.0-rc.1` under the `next` tag on npm). The stable number moves only at release. -- **The founder sets the number for every release.** Open a PR with the code; the number is applied at the release step. +- **The first slot stays `1`.** It is never bumped. +- **Rebuilt or added behaviour** → minor +1, patch resets to 0 (`1.3.x` → `1.4.0`). +- **Fixed or adjusted existing behaviour** → patch +1 (`1.3.0` → `1.3.1`). +- **Always +1 numerically.** Never append digits, never skip. +- **Existing callers keep working.** A renamed option or method ships next to the old name, which keeps working (marked deprecated). A change that cannot be made that way is the founder's decision. +- **Pre-release for testers, only if needed:** the same number with an `rc` suffix (`1.4.0rc1`). The stable number moves only at release. +- **The founder sets the number for every release.** Open a PR with the code; the number is applied at the release step (version in `pyproject.toml` and `src/agentchatme/_version.py`, CHANGELOG section, then the `v` tag; `publish.yml` refuses a tag that differs from either file). -History: before 2026-11-02 numbers were bumped by appending a digit (`0.2.3` → `0.2.31` → `0.2.311`), which inflated the patch slot into the millions. Version comparison is per slot, numerically, so `0.7.9` is OLDER than `0.7.8211111`. Each package's next release is therefore one minor bump to a clean number, and the rule above applies from there. +History: in July 2026 numbers were bumped by appending a digit (`1.0.3` → `1.0.31` → `1.0.32` → `1.0.321`). Version comparison is per slot, numerically, so `1.0.4` would have sorted older than `1.0.321`. `1.1.0` went back to clean numbers, and the rule above (written down on 2026-11-02) keeps them clean. diff --git a/pyproject.toml b/pyproject.toml index 98ae3b9..72f162b 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -4,7 +4,7 @@ build-backend = "hatchling.build" [project] name = "agentchatme" -version = "1.3.0" +version = "1.3.1" description = "Official Python SDK for AgentChat — the messaging platform for AI agents. Mirrors the npm package name: agentchatme (TypeScript) ↔ agentchatme (Python)." readme = "README.md" license = "MIT" diff --git a/src/agentchatme/_version.py b/src/agentchatme/_version.py index b6806b0..6674d56 100644 --- a/src/agentchatme/_version.py +++ b/src/agentchatme/_version.py @@ -5,4 +5,4 @@ test suite asserts they match. """ -VERSION = "1.3.0" +VERSION = "1.3.1" From 673cfb3ba7682a639629362d5cbb70f2e21b3051 Mon Sep 17 00:00:00 2001 From: San Date: Wed, 11 Nov 2026 02:31:56 -0800 Subject: [PATCH 2/2] release review: README changes in the 1.3.1 notes, absolute VERSIONING 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. --- CHANGELOG.md | 12 ++++++++---- VERSIONING.md | 2 +- 2 files changed, 9 insertions(+), 5 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index d70451e..7953304 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -2,7 +2,9 @@ All notable changes to the `agentchatme` Python SDK are documented in this file. The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), -and version numbers follow [VERSIONING.md](VERSIONING.md). The on-the-wire +and version numbers follow +[VERSIONING.md](https://github.com/agentchatme/agentchat-python/blob/main/VERSIONING.md). +The on-the-wire API is versioned separately under `/v1/...`. ## [1.3.1] — 2026-11-11 @@ -24,9 +26,11 @@ API is versioned separately under `/v1/...`. or reporting a system agent; deleting or rotating a system account's key through the public API) and no longer calls system agents a support channel. -- README samples: `send_message` takes `text=`, `CallOptions` is passed as - a dataclass, and "unanswered" wakes come only on a socket created with - `capabilities={"rewake": True}`. +- README: the samples send with `text=` (or `type="file"` and + `attachment_id=`), pass `CallOptions` as a dataclass, and note that + "unanswered" wakes come only on a socket created with + `capabilities={"rewake": True}`; the Links section points at the SDK + guide, the integration contract v1 and the REST API reference. ## [1.3.0] — 2026-11-08 diff --git a/VERSIONING.md b/VERSIONING.md index e417bc7..0e9633b 100644 --- a/VERSIONING.md +++ b/VERSIONING.md @@ -6,7 +6,7 @@ Semantic Versioning, as applied to this package. It has been `1.x` on PyPI since - **Rebuilt or added behaviour** → minor +1, patch resets to 0 (`1.3.x` → `1.4.0`). - **Fixed or adjusted existing behaviour** → patch +1 (`1.3.0` → `1.3.1`). - **Always +1 numerically.** Never append digits, never skip. -- **Existing callers keep working.** A renamed option or method ships next to the old name, which keeps working (marked deprecated). A change that cannot be made that way is the founder's decision. +- **A change that would break existing callers** has no slot of its own under this rule: whether and how to make one is the founder's decision. - **Pre-release for testers, only if needed:** the same number with an `rc` suffix (`1.4.0rc1`). The stable number moves only at release. - **The founder sets the number for every release.** Open a PR with the code; the number is applied at the release step (version in `pyproject.toml` and `src/agentchatme/_version.py`, CHANGELOG section, then the `v` tag; `publish.yml` refuses a tag that differs from either file).