Skip to content

chore(release): 3.9.3 - #233

Merged
acidkill merged 1 commit into
mainfrom
release/3.9.3
Sep 7, 2026
Merged

acidkill merged 1 commit into
mainfrom
release/3.9.3

Conversation

@acidkill

@acidkill acidkill commented Sep 7, 2026

Copy link
Copy Markdown
Owner

Summary

Release 3.9.3. Version bumped across all 16 version-bearing locations, with a CHANGELOG.md section covering everything since 3.9.2: the two remote-topology fixes found while deploying 3.9.2 against SurrealDB over wss.

PATCH rather than MINOR: one configurable-env knob (#231, closes the stopgap half of #229 — root-cause stays open there) and one schema-convergence fix (#232, closes #230); no new surface beyond the env var.

Why

Deploying 3.9.2 on the remote topology exposed both issues live: MCP tool calls dying at the hardcoded 30 s while the CLI succeeded, and the legacy SCHEMALESS change_log table rejecting the payload … FLEXIBLE define on every startup.

Contents

Test plan

  • python scripts/pre_ship.py — all 10 sections pass (16/16 at 3.9.3, CHANGELOG check, ruff, mypy, fast suite, docs gates).
  • Both content PRs green on all 9 CI checks before merge.
  • Post-publish: confirm artefacts on PyPI, npm (plugin + SDK), ClawHub, VS Code Marketplace — publish steps are failure-tolerant, a green job is not proof.

Verified by

@acidkill

@acidkill
acidkill marked this pull request as ready for review September 7, 2026 12:04
@acidkill
acidkill merged commit 796ad65 into main Sep 7, 2026
9 checks passed
@acidkill
acidkill deleted the release/3.9.3 branch September 7, 2026 12:04
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.

ensure_schema warns on every startup when change_log exists as a legacy SCHEMALESS table (DEFINE FIELD … FLEXIBLE rejected)

1 participant