Skip to content

v1.3.3

Choose a tag to compare

@abruption abruption released this 30 Oct 01:45
Immutable release. Only release title and notes can be modified.
fee7fb8

v1.3.3 maintenance preparation

Prepared on 2026-10-30 against published v1.3.2. At that preparation checkpoint, v1.3.3 was an unpublished candidate. The integrated source base is ec2f7fc808f1e22519348091d51c28a2fd522caf, before version preparation; it is not the final release commit. This work prepares a reviewable change only. It does not authorize merge, tag creation or publication.

Changes

  • #349 / #352: refresh the PR template to default to non-closing Refs, make intentional completion explicit, and request relevant validation and version evidence. A read-only warning uses code from trusted main and a limited PR-body heuristic. It neither executes body text nor writes issue state, and it is not GitHub's complete closing-reference parser or a guarantee against closure.
  • #350 / #353: extend standard, GIL-enabled CPython 3.14 CI on Ubuntu/macOS. Core covers 3.9/3.13/3.14 on Ubuntu/macOS and retains Windows 3.13; MCP keeps SDK floor 1.30.0 and latest compatible 1.x profiles across 3.10/3.13/3.14 (12 cells), and Relay covers 3.11/3.13/3.14 (6 cells). Three packaging/install cells cover Ubuntu 3.13, Ubuntu 3.14 and macOS 3.14. The classifier includes 3.14; Python floors remain core 3.9, MCP 3.10 and Relay 3.11. See the source test matrix.
  • #351 / #354: use version-neutral publication guidance in current READMEs, add a separate dated v1.3.2 publication record, preserve historical preparation records, make the existing post-publication checklist explicit, and correct the four-language Direct guide's stale unpublished label.
  • Synchronize the compatibility snapshot and prospective SKILL.md support asset to the independently published Python skill v0.4.1. This is a compatibility-copy update, not a new skill release or an update to separately installed skills.

Exact source and compatibility

The merged sources are #352 6f9026e46138db544fb9c990387fcd4ccf37400f, #353 88f2c906e3f4bae8b377fcfac049a65fd68dea64 and #354 ec2f7fc808f1e22519348091d51c28a2fd522caf.

The skill snapshot comes from commit 263b0c333d539dc4e885b16ae3369a26f33097d8 in abruption/session-peer-skill at tag v0.4.1, annotated tag object ba08d19af33cad0f7d032b7fe18c82d6ddd6793f: 27126 UTF-8 bytes, SHA-256 fdf5697c04f4a37194986622afb3a7966bb02631c128cf18a323e3fbe5ae90ed. Its version is 0.4.1, basic runtime minimum 0.9.1, documented CLI coverage 1.3.2 and receiver codexBin floor 1.0.1. These numbers are independent of runtime 1.3.3. The support copy is outside the Python wheel/sdist.

Boundaries and release gates

The 3.14 checks are fixture and package validation, not new live native-agent, Windows 3.14 or free-threaded Python acceptance. The version bump and documentation changes add no runtime authentication, protocol, delivery or ACK behavior. Existing unknown-outcome/no-automatic-resend and experimental-feature boundaries remain.

Integrated-base CI and CodeQL succeeded for the source base above. These results do not replace checks of the preparation head or final protected-main source. The 10 new 3.14 cells passed in the initial CI before the classifier was added, and the updated full CI passed after that addition.

Keep all published v1.3.2 tags/assets and its dated records unchanged. Review the exact preparation head and require successful current-head checks, then successful protected-main CI before any later release step. A separately authorized publication must verify all 7 frozen assets, including SHA256SUMS and release-provenance.json, against the exact tag/source and authenticated attestations, test fresh installations and retain the required human PyPI environment approval. Skipping a private PyPI login/binding recheck does not waive that approval. Use the existing post-publication documentation checklist after actual GitHub and PyPI evidence exists; do not announce availability in advance.

Preparation performs no service deployment/restart, global installation or independent skill publication. Node Control deployment and receiver/skill environment updates remain separately authorized operations.