Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 20 additions & 3 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,10 +2,12 @@

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](https://github.com/agentchatme/agentchat-python/blob/main/VERSIONING.md).
The on-the-wire
API is versioned separately under `/v1/...`.

## [Unreleased]
## [1.3.1] — 2026-11-11

### Fixed

Expand All @@ -15,6 +17,21 @@ 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: 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

Contract v1 (the finished receive gate). A host that upgrades without
Expand Down
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
16 changes: 9 additions & 7 deletions VERSIONING.md
Original file line number Diff line number Diff line change
@@ -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.
- **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<version>` 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.
2 changes: 1 addition & 1 deletion pyproject.toml
Original file line number Diff line number Diff line change
Expand Up @@ -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"
Expand Down
2 changes: 1 addition & 1 deletion src/agentchatme/_version.py
Original file line number Diff line number Diff line change
Expand Up @@ -5,4 +5,4 @@
test suite asserts they match.
"""

VERSION = "1.3.0"
VERSION = "1.3.1"
Loading