chore(deployments): pin threadplane-middleware 0.1.0 - #1068
Merged
Conversation
…rry emit_custom_event 0.1.0 is live on PyPI, so the Railway lanes can move off the 0.0.1 pin. Until now emit_custom_event shipped in the repo but was not importable in the deployed images, which install from the exported requirements. Bumped by upgrading each uv.lock and re-running `uv export`, then regenerating deployments/ag-ui-dev via the generator — these files carry GENERATED headers and must not be hand-edited. The diff is confined to the middleware pin, its URLs and hashes. Verified the published wheel actually contains custom_events.py, that it wraps adispatch_custom_event, and that emit_custom_event is exported. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
blove
enabled auto-merge (squash)
September 8, 2026 20:01
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.
threadplane-middleware@0.1.0is live on PyPI with attestations on both files, so the Railway lanes can finally move off the0.0.1pin.This closes the ordering gap from the release:
emit_custom_eventhas been in the repository since #1052, but the deployed images install from the exported requirements, which pinned0.0.1— so the helper was not importable where it matters. The pin could only be bumped after the package was published, or the image build would fail on a version that did not exist.How it was bumped. These files carry
GENERATED/autogenerated by uvheaders, so nothing was hand-edited: each project'suv.lockwas upgraded withuv lock --upgrade-package threadplane-middleware, requirements re-exported withuv export --no-hashes, anddeployments/ag-ui-devregenerated throughscripts/generate-ag-ui-deployment-config.ts. The declared constraints (>=0.0.1/>=0.0.2) already admitted 0.1.0 and are unchanged.Verification
custom_events.py, that the helper wrapsadispatch_custom_event, and that it is exported from the package.nx test scriptsgreen (it guards the generator's output).🤖 Generated with Claude Code