release: 0.14.2 - #897
Merged
Merged
release: 0.14.2#897
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Open pull requests citing the same issues:
If one already covers this change, review or build on it instead of racing it (CONTRIBUTING.md "Overlapping work"). |
sv
added a commit
that referenced
this pull request
Sep 23, 2026
## What This PR cuts **0.14.3**. The same file set as #897 changes: - the CHANGELOG section gets its date; - the version is bumped in the files the service, the MCP wrapper and the worker share; - the measured block of `sz-baseline.json` is re-ratcheted. No cap moves. ## Why One change has landed since v0.14.2: #898. Room writes no longer queue behind the periodic stats snapshot. At ~239k rooms the snapshot pass holds its lock ~4.7 s every 300 s, and 91 writers were measured waiting behind it on the live box. The release is PATCH because nothing on the HTTP surface changes. #898 adds 2 core lines to `store.py` (1023 → 1025, under its cap of 1030). The push-only `sz.py --check` on main therefore fails until this re-ratchet lands, as it did before #897. After merge, tag `v0.14.3` on the squash commit. That publishes `ghcr.io/flop-labs/technocore-chat:0.14.3`, and the box's autoupdate timer installs it within ~15 min. ## Checks - [x] `uv run coverage run -m pytest tests -q && uv run coverage report`: 813 passed, 98.01% - [x] `uv run ruff check . && uv run ruff format --check .` and `uv run ty check`: clean - [x] `uv lock --check`, run for the root and for `mcp/worker` after `uv build --project mcp` built the 0.14.3 wheel - [x] `sz.py --caps` and `sz.py --check` - [x] both `release.yml` gates - [x] Docs that would now be wrong are updated: `CHANGELOG.md` is the change - [x] New surface on a world-writable service: nothing new
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
1 participant
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.
What
Cuts 0.14.2. Like #893, it dates the CHANGELOG section, bumps the version in the files the service, the MCP wrapper and the worker share, and re-ratchets the measured block of
sz-baseline.json. No cap moves.Why
Main CI is red. Since #163, every push to main fails
sz.py --check(core/limit.py 183 -> 186, under its cap of 193). Because that step fails, the steps after it are skipped on main: the example e2e, the MCP wrapper build, and the image build and smoke. This PR's CI runs those steps against #163 and #126 for the first time.There are three fixes since v0.14.1, all PATCH, and nothing on the HTTP surface moves:
/r/<room>/exportstreams again instead of buffering to near-EOF.open()as absent, where they used to return a 500.After merge: tag
v0.14.2on the squash commit, which publishesghcr.io/flop-labs/technocore-chat:0.14.2.Checks
uv run coverage run -m pytest tests -q && uv run coverage report: 812 passed, 98.08%uv run ruff check . && uv run ruff format --check .anduv run ty check: cleanuv lock --check(root, andmcp/workerafteruv build --project mcpbuilt the 0.14.2 wheel),sz.py --caps,sz.py --check, and bothrelease.ymlgatesCHANGELOG.mdis the change