Repository navigation
0.6.0: accept zmqruntime 0.6 (L3) - #37
Merged
Merged
Conversation
zmqruntime 0.6 renames its runtime vocabulary and declares its messages; PolyStore uses only the ACK route, image transfer identity, queue tracker, viewer protocol and ZMQConfig, whose APIs are unchanged. The bound moves to zmqruntime>=0.6,<0.7. uv.lock regenerates once zmqruntime 0.6.0 is published (no registry release of it exists yet to lock against). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
OpenHCS consolidation surface L3. 0.5.0 → 0.6.0.
zmqruntime 0.6 (OpenHCSDev/ZMQRuntime#28) renames its runtime vocabulary and declares its messages. PolyStore uses only the ACK route, image-transfer identity, queue tracker, viewer protocol and
ZMQConfig, whose APIs are unchanged, so the only change is the bound:zmqruntime>=0.6,<0.7(minor bump because the old bound<0.6excludes the new runtime).Local:
pytest testsagainst the zmqruntime PR branch: 594 passed, 2 skipped.CI and
uv.lock:uv lockcannot resolve until zmqruntime 0.6.0 is on PyPI (only zmqruntime<=0.5.0 is available), so the lock is not regenerated in this PR and thedistribution/install jobs will fail until then. At release: publish zmqruntime 0.6.0, then runuv lockon this branch and push.Not merged or tagged; the owner releases.
L3 · PolyStore PR · src −0 +0 · tests −0 +0 (pyproject only)
🤖 Generated with Claude Code