Skip to content

chore(deps): batch compose, Python and CI action updates - #251

Merged
jsugg merged 1 commit into
mainfrom
chore/deps-batch-2026-11
Nov 11, 2026
Merged

jsugg merged 1 commit into
mainfrom
chore/deps-batch-2026-11

Conversation

@jsugg

@jsugg jsugg commented Nov 11, 2026

Copy link
Copy Markdown
Owner

Summary

Lands the compatible updates from the Dependabot wave in one batch and moves every companion pin with them. All six updates are merged here, none are held.

Each Dependabot PR failed CI only because it bumped the base file. The copies that carry the same pin were left behind:

  • Compose images: the hosted-macOS variants (docker-compose.*.ci-hosted-macos.yaml), the packaged mirror under src/clawops/assets/platform/compose/, and the image literal in test_platform_verify.py.
  • Action SHAs: test_devflow_ci_contract.py and test_ci_workflow_surfaces.py assert the exact pins.

The mirror was regenerated with make sync-runtime-assets (tests/scripts/sync_runtime_assets.py), not edited by hand.

The security / Run Repository Quality and Runtime Security Scans failure on #245 and #246 is not a code problem. It comes from the independent-review gate in tests/utils/helpers/_ci_workflows/security.py. Dependabot is the author and the PR touches pyproject.toml and uv.lock, so the gate wants a non-author approval. A maintainer-authored PR passes the same gate because the repo has no other collaborator with write access.

Updates

neo4j compose image (#241)

From -> to neo4j:5.26.23-community -> neo4j:5.26.31-community@sha256:c7d25c0e…8069
Evidence 5.26.31 release notes: a Jackson upgrade for CVEs, with bundled APOC/Browser bumps. The digest was checked against Docker Hub and is a multi-arch index (amd64, arm64).
Compatibility Patch release on the same 5.26 LTS line. The store format is unchanged and existing data volumes open as-is. Apple Silicon and Intel are both covered by the index.
Companion files platform/compose/docker-compose.aux-stack.yaml, platform/compose/docker-compose.aux-stack.ci-hosted-macos.yaml, both packaged mirrors, tests/suites/integration/clawops/test_platform_verify.py

playwright compose image (#242)

From -> to mcr.microsoft.com/playwright:v1.41.1-jammy -> v1.65.0-jammy@sha256:5a8620d7…dc04
Evidence The digest was checked against MCR and is an index with amd64 and arm64. The base is still Ubuntu 22.04 (jammy). In this repo the container runs sleep infinity and consumers attach over CDP on 127.0.0.1:9222. No Playwright client is pinned in the repo, so there is no client/server protocol version to match.
Compatibility cdpUrl in platform/configs/openclaw/60-browser-lab.json5 is unchanged. The /workspace/state volume holds only operator-created content. A newer Chromium migrates profiles forward but cannot downgrade them. arm64 compressed size grows from 677 MB to 929 MB, which is still inside the 3 GB hosted-docker budget in tests/utils/helpers/_hosted_docker/disk.py. The fresh-host Browser Lab lanes test the real pull.
Companion files platform/compose/docker-compose.browser-lab.yaml, platform/compose/docker-compose.browser-lab.ci-hosted-macos.yaml, both packaged mirrors

tree-sitter (#245)

From -> to tree-sitter==0.26.0 -> 0.26.1
Evidence v0.26.1 release: reference-leak and NULL-dereference fixes, an is/is-not predicate fix, and a typing cleanup. The API is unchanged. Wheels exist for cp312 and cp313 on macOS x86_64, macOS arm64, and Linux.
Compatibility Patch release with no grammar ABI change (the grammar pins stay at 0.25.x). Python 3.12+ is covered.
Companion files pyproject.toml, uv.lock

neo4j Python driver (#246, major)

From -> to neo4j>=5.26,<6 (5.28.3) -> neo4j>=6.4.1,<7 (6.4.1)
Evidence 6.x changelog. The Neo4j supported-versions matrix lists driver 6.x for server 5.26 LTS. 6.4.1 declares requires-python >=3.10. The removed APIs (read_transaction/write_transaction, Bookmark, the trust option, the neo4j-driver alias, raw string bookmarks) are not used in src/.
Behaviour change handled Drivers are no longer closed in __del__. 6.x only emits an unclosed-resource warning. Neo4jGraphBackend now has an idempotent close(). CodebaseContextService is a context manager, and the clawops context CLI and both workflow_runner call sites use it. The long-running worker command and multi-step workflows therefore no longer leak connection pools.
Typing fix 6.x imports its typing alias as from .. import _typing as t. Pyright cannot resolve t.TYPE_CHECKING through that alias and falls back to the untyped **config signatures, which is the cause of the 3 strict errors on #246. A narrow Protocol now types the driver surface, cast once at the dynamic-import boundary. This follows the existing tree-sitter grammar loader pattern and adds no suppressions.
Compatibility Same server (5.26 LTS) and same Bolt URIs. Existing graph.neo4j_url configs work unchanged, and no graph data format is involved.
Companion files pyproject.toml, uv.lock, src/clawops/context/codebase/service.py, src/clawops/workflow_runner.py, tests/suites/unit/clawops/context/test_codebase_graph.py (new lifecycle tests)

astral-sh/setup-uv (#247, major)

From -> to v7.6.0 (37802adc) -> v10.3.3 (68559e99, tag SHA verified)
Evidence Breaking changes per the releases: v8 removed the legacy manifest format and the floating major/minor tags. v9 changed the default prune-cache to false. v10 makes enable-cache: auto skip pull_request_target, workflow_run, and release, and adds .tool-versions Python handling.
Compatibility Every use site pins version: "0.10.9" (except the pre-commit job, which was already unpinned) and sets enable-cache: true explicitly, so the auto change does not apply. No manifest, .tool-versions or python-version input is used. The runtime is still node24. Caches are no longer pruned before save, which trades slightly larger cache entries for less PyPI load (upstream rationale, #967). uv.lock stays at revision = 3 and passes uv lock --check under the CI-pinned uv 0.10.9.
Companion files All workflows that use it, tests/suites/contracts/repo/test_devflow_ci_contract.py, tests/suites/contracts/repo/test_ci_workflow_surfaces.py

actions/setup-python (#248, major)

From -> to v6.3.0 (ece7cb06) -> v7.1.0 (6d4fd22b, tag SHA verified)
Evidence v7.0.0: ESM migration and removal of the pip-install input. v7.1.0: new mirror and mirror-token inputs plus dependency bumps.
Compatibility The runtime is node24 in both v6.3.0 and v7.1.0. The repo only passes python-version, and pip-install is not used.
Companion files All workflows that use it, tests/suites/contracts/repo/test_devflow_ci_contract.py

Local gates

  • make lint: all checks passed
  • make typecheck: mypy and pyright both report no issues
  • make test-unit: passed
  • make test-contracts: passed
  • pytest -m devflow: passed
  • uv lock --check with uv 0.10.9: passed

Supersedes #241, #242, #245, #246, #247, #248.

Land the compatible updates from Dependabot #241, #242, #245, #246,
#247 and #248 in one change, with every companion pin moved in sync.

- neo4j image 5.26.23 -> 5.26.31 (5.26 LTS patch), base and
  hosted-macOS compose variants plus the packaged mirror
- playwright image v1.41.1-jammy -> v1.65.0-jammy, same companions
- tree-sitter 0.26.0 -> 0.26.1
- neo4j driver 5.28.3 -> 6.4.1
- astral-sh/setup-uv v7.6.0 -> v10.3.3
- actions/setup-python v6.3.0 -> v7.1.0

neo4j 6 no longer closes drivers on garbage collection, so the graph
backend now closes its cached driver explicitly and the codebase context
service is a context manager used by the CLI and the workflow runner.
neo4j 6 also hides its typed driver signatures behind a private
TYPE_CHECKING alias that pyright cannot resolve; a narrow Protocol now
types the driver surface at the import boundary.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant