Repository navigation
release: 0.4.0 - #103
Merged
Merged
release: 0.4.0#103
Conversation
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
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.
Release 0.4.0, the production-ready release for the tier the operations guide describes. Fixes #82.
The changelog's Unreleased section becomes
0.4.0dated 2026-10-26, with a new empty Unreleased heading above it and the compare links updated. README and AGENTS.md replace "experimental prototype" with the supported tier: an internal service for applications that own their host and network, one or more instances each answering its own jobs, behind the operator's TLS and the application's own authentication, the job table kept across a restart byBRIDGE_STATE_DIR; not for public exposure of the worker, nor for throughput beyond the measured figures without more instances. The version mentions move tov0.4.0and^0.4; the testing guide's sentence about first-job model loading now describes loading at child start; the operations guide, the security boundaries, SECURITY.md and the testing guide's closing paragraph no longer call the project experimental and state precisely what a restart does. No code changes.What 0.4.0 holds since 0.3.0, every slice merged through its own reviewed pull request: drain on shutdown with
503when busy, a header cap and/readyz; optional structured JSON logging; a per-owner capacity cap; mypy at strict and ruff in CI; published worker images for amd64 and arm64 with a tag-triggered publish workflow; dependency audits, Dependabot for pip and composer, CodeQL and a security policy; measured reranking and NER quality on public datasets, measured throughput and latency under load, and the corrected Masked column; the operations guide; the README's two use cases; the Sponsors funding file.Files:
CHANGELOG.md,README.md,AGENTS.md,docs/operations.md,docs/security.md,docs/testing.md,docs/integration.md,SECURITY.md.Checks on this head: the full deterministic sequence (python-tests, PHP contract and HTTP checks with the two-token worker, FrankenPHP integration, MCP suite, consumer install, PHPStan at level max, PSR-18 checks, Laravel and Symfony tests, the TLS check, ruff and mypy). Review: independent read by Codex (gpt-6.1-sol) of every changed sentence against the measured tables and the code: mergeable as is. After the merge: tag
v0.4.0on the merge commit and the GitHub release from the 0.4.0 section, which also runs the publish workflow for the images; both on the owner's yes.