Repository navigation
#153 chore: catch up co-core 0.37.0 -> 0.39.1 - #155
Merged
Merged
Conversation
Two-minor catch-up (0.37 -> 0.39) ahead of the capture consumer (#138), so the wheel diff doesn't land with a behaviour change. Lock resolves 0.39.1; nothing else in the lock moves. The closure diff (scripts/co_core_closure_diff.py 0.37.0 0.39.1) is pasted into the pin comment. Nothing reached from src/ or scripts/ moved: the capture models and CONTENT_CAPTURE are added, from_wire learns three capture event types, and pure/extract/* changed (0.38's JSON extractor), loaded only via changes.py and called nowhere here. Floor 0.39.0, not 0.39.1: 0.39.0 -> 0.39.1 is __version__ only. Co-authored-by: Shelley <shelley@exe.dev>
…fest Version swap at the same length in AGENTS.md (14090 bytes, est. 5991/6000 tokens). DEPLOYMENT.md's lazy-import line moves to 0.39.1, re-measured: the same two co-core-sync sites. The manifest description changed, so codebase_update follows the merge. Co-authored-by: Shelley <shelley@exe.dev>
… every doc that names it Three identical specifiers, one minor wide, and AGENTS.md, DEPLOYMENT.md and the SocratiCode manifest each naming it. Red against 5ed0219 (pin moved, docs stale: 3 failed) and against one skewed specifier; green at HEAD. Co-authored-by: Shelley <shelley@exe.dev>
…37.0 class unchanged bar docstrings The six-model field-name check understated the evidence and overstated its reach. A whole-file class comparison, docstrings stripped, finds every pre-existing class in changes.py identical; InfoItemPrimaryChangedEvent and ProcessingFailedEvent differ in docstrings only. Also untangles the co_core_aio sentence. Co-authored-by: Shelley <shelley@exe.dev>
Command streams still dead-letter it, under the wrong-type reason rather than as a poison frame; the policy reader skips it with a wrong-type warning rather than a poison skip. Co-authored-by: Shelley <shelley@exe.dev>
Open
1 of 6 tasks
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.
Closes #153.
co-core,co-core-aio[bus,gcs],co-core-sync[gcs]→>=0.39.0,<0.40; the lock resolves 0.39.1 and nothing else in it moves.scripts/co_core_closure_diff.py 0.37.0 0.39.1) is pasted verbatim into the pin comment, with each changed file read by hand. Nothing Replicator reaches moved.tests/test_co_core_pin.pykeeps those sites and the three specifiers in step.Brief review: #153 (comment)
Report and post-merge steps: #153 (comment)