Repository navigation
#199 co-core 0.45 → 0.46, one-minor catch-up - #200
Merged
Merged
Conversation
One minor, in #192's shape; the lock takes 0.46.1, the index's newest (probed at <1). The closure diff 0.45.0 -> 0.46.1 is 58/58 with three `version-only` files and no `changed` one; 0.46.0's co/v1 read-path changes sit outside the closure, and 0.46.1's soupsieve floor is under an extra not declared here. The report is in the pin comment, and the lock moves the three co-core entries only. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…e manifest DEPENDENCIES.md's dynamic-import note now reads at 0.46.1, where the closure diff found the same two co-core-sync sites. The manifest description owes a codebase_update, run from the main checkout after the merge (SocratiCode indexes the main checkout's absolute path, never a worktree). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
41 of 43 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 #199. This PR doesn't close the issue. Closure waits for the post-merge restart and read-back on the issue.
Moves co-core, co-core-aio and co-core-sync from
>=0.45.0,<0.46to>=0.46.0,<0.47. The lock takes 0.46.1 ×3 from the co-pypi index, with hashes. No code change.The closure diff 0.45.0 → 0.46.1 is 58/58 files, with three
version-onlyand nothingchanged. It's the same withtests/as a root.[extract], which isn't declared here. soupsieve isn't inuv.lock.Changes
pyproject.toml: the pins and the pin comment.uv.lock: the threeco-core*entries and the requires-dist mirror, nothing else.tests/test_dependency_index.py: the bound moves to>=0.47. It went red on the lock move, as expected, then green.AGENTS.md,docs/DEPENDENCIES.md,.socraticodecontextartifacts.json: the version literals. The manifest'scodebase_updateruns after the merge, from the main checkout.Local gates on
d6d9d39, isolated worktree venv:-m integration: 57;-m browser: 31;tests/ci: 44;uv lock --check: clean.🤖 Generated with Claude Code