Repository navigation
#211 Catch up co-core 0.48 → 0.50 (0.50.0) - #213
Merged
Merged
Conversation
All three pins move to >=0.50.0,<0.51; the lock takes 0.50.0, the index's newest with the bound opened to <1. The pin comment carries the 0.48.2 → 0.50.0 closure-diff report and the two changed files read by hand (Drive-only gdrive.py; transport.py's #714 deadline fix, loaded but never mounted here). The index test's bound moves to >=0.51. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
42 of 44 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.
Refs #211
Moves the
co-core,co-core-aioandco-core-syncpins from>=0.48.0,<0.49to>=0.50.0,<0.51. The lock takes 0.50.0 ×3, the index's newest with the bound opened to<1[measured 2026-11-18T13:13Z]. No code change. The pickup corrections to the brief are on #211.What moved
uv.lock: threeversionlines, the threerequires-distspecifiers, and their url and hash lines. Nothing else moved.uv lock --checkis clean, and each 0.50.0 wheel's sha256 appears in the lock.pyproject.toml) carries theco_core_closure_diff.py 0.48.2 0.50.0report verbatim, from the locked wheels. It's 6 not identical: 3version-only,changes.pydocstrings-only, and 2changed. Bothchangedfiles arrived in 0.49.0; I read them by hand:drivers/gdrive.pyis Drive-only and can't load here.drivers/transport.pyis cannobserv#714's deadline fix. It's loaded at worker import, but nothing in the three wheels or in this repo mounts its adapter.InformationModel.source's removal ships in co-core's own wheel, and it's still outside this closure.AGENTS.md,docs/DEPENDENCIES.md(the pin, and "At 0.50.0 …"), and the manifest description. That description owes acodebase_update, which I'll run from the main checkout after the merge.tests/test_dependency_index.py: the bound moves to>=0.51. The test was red on the lock move before that edit.Gates (worktree, isolated venv)
796186f: 2062 / 1)-m integration(scratch redis-server)-m browser(delegated user scope)-m gcstests/ciThe deploy of the merge commit restarts the worker.
🤖 Generated with Claude Code