chore(acp): bump codebuddy and dimcode registry pins to probed versions - #931
Merged
Conversation
kaizhou-lab
added a commit
that referenced
this pull request
Aug 25, 2026
…obed versions (#934) ## Summary Scheduled ACP Registry version sync. Four npx pins drifted since #931, each backed by a fresh serial ACP probe of the exact pinned version. The diff is the lock file plus the one lock-derived test assertion that embeds codebuddy's version. | backend | package | old → new | initialize | session/new | |---|---|---|---|---| | codebuddy | `@tencent-ai/codebuddy-code` | 2.138.0 → **2.139.0** | ok (protocolVersion 1) | auth required (`-32000`, `data.category: auth`) | | dimcode | `dimcode` | 0.3.19 → **0.3.20** | ok (agentInfo version 0.3.20) | auth required (`-32000`, "Provider credentials are required") | | glm-acp-agent | `glm-acp-agent` | 1.6.0 → **1.6.1** | ok (protocolVersion 1) | **succeeded** unauthenticated | | grok | `@xai-official/grok` | 1.0.8 → **1.0.10** | ok (protocolVersion 1) | auth required (`-32000`, "no auth method id provided") | All four meet the release-lock criterion: `initialize` succeeds, and `session/new` either succeeds or returns a clearly classified authentication requirement. Probes ran serially with no inherited HOME or credentials. glm-acp-agent's session opened without auth and advertised `thought_level`, `mode`, and `model` option categories, including a `bypass_permissions` mode value. That is recorded as probe evidence only — this PR changes no metadata, so no `yolo_id` or mode data is derived from it. It also continues to self-report `agentInfo.version` as `1.0.0` while the package is 1.6.1; a standing vendor quirk, not an AionCore defect. **Derived assertion updated:** `registry_npx_lock.rs` pins codebuddy's exact version inside a `--package`-form argument list, so it moves with the lock — `2.138.0` → `2.139.0`. Every outgoing version (`2.138.0`, `0.3.19`, `1.6.0`, `1.0.8`) was grepped across `crates/**/*.rs` before committing; codebuddy's was the only real assertion, and the remaining textual matches are unrelated (a codex sample path, a Windows socket error code). `npx_cache_repair.rs` keeps its own version literals: those are cache-path hash fixtures, not lock assertions, and changing them would break their hash expectations. The other 7 Registry-pinned packages (autohand, deepagents, dirac, kilo, nova, pi, sigit) match the snapshot exactly. Package names and entrypoint args are unchanged for all 11. Drifted but not upgraded: none. `mimo-code` remains the one non-Registry builtin (no `registry_json_id`), excluded from drift reconciliation. ## Registry snapshot - Audit pinned to release tag [`v2026.08.25-fbfe844`](https://cdn.agentclientprotocol.com/registry/v1/v2026.08.25-fbfe844/registry.json) of `agentclientprotocol/registry`, fetched via the versioned CDN path for reproducibility. - 39 ids in the snapshot: no newly listed and no delisted agents versus the baseline. (`antigravity-acp` remains listed and deferred as binary-only since 2026-08-21; `fast-agent` and `minion-code` remain listed but uvx-only and therefore out of scope.) ## Validation - `just migration-check` — pass - `just lint-fix` (`cargo fix` + `clippy --fix --workspace -D warnings`) — clean - `just fmt` — clean - **Local `cargo nextest` intentionally skipped, by standing policy for lock-only bumps** (established 2026-08-11). The Test check on this PR is the authority for this change: the merge decision depends on CI rather than the local run, and this host's load only manufactures timeout-shaped test failures, which nothing in the local steps above is subject to. ## Logging No logging changes: lock version bumps plus one test assertion; existing startup/session error paths already identify a failing agent by backend. Co-authored-by: zk <>
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
1 participant
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.
Summary
Scheduled ACP Registry version sync. Two npx pins drifted since #921, each backed by a fresh serial ACP probe of the exact pinned version. The diff is the lock file plus the one lock-derived test assertion that embeds codebuddy's version.
@tencent-ai/codebuddy-code-32000, categoryauth)dimcode-32000, "Provider credentials are required")Both meet the release-lock criterion:
initializesucceeds andsession/newreturns a clearly classified authentication requirement. Probes ran serially with no inherited HOME or credentials. codebuddy's--acpentrypoint is unchanged across the minor bump.Derived assertion updated:
registry_npx_lock.rspins codebuddy's exact version inside a--package-form argument list, so it moves with the lock —2.137.1→2.138.0. This is the same assertion that broke CI in #909 when a package-name regex missed it; the per-version scan introduced afterwards (grep each OUTGOING version acrosscrates/**/*.rs) caught it before push this time. dimcode's0.3.18has no such assertion.npx_cache_repair.rskeeps its own version literals: those are cache-path hash fixtures, not lock assertions, and changing them would break their hash expectations.The other 9 Registry-pinned packages (autohand, deepagents, dirac, glm-acp-agent, grok, kilo, nova, pi, sigit) match the snapshot exactly. Package names and entrypoint args are unchanged for all 11. Drifted but not upgraded: none.
mimo-coderemains the one non-Registry builtin (noregistry_json_id), excluded from drift reconciliation.dimcode continues to self-report
agentInfo.titleas "DimAgent" against a public listing that says "DimCode" — the standing observation since #814; no metadata change.Registry snapshot
v2026.08.24-06dfed0ofagentclientprotocol/registry, fetched via the versioned CDN path for reproducibility.antigravity-acp, deferred as binary-only since 2026-08-21).Validation
just migration-check— passjust lint-fix(cargo fix+clippy --fix --workspace -D warnings) — cleanjust fmt— cleancargo nextestintentionally skipped, by standing policy for lock-only bumps (established 2026-08-11). The Test check on this PR is the authority for this change: the merge decision depends on CI rather than the local run, and this host's load only manufactures timeout-shaped test failures, which nothing in the local steps above is subject to.Logging
No logging changes: lock version bumps plus one test assertion; existing startup/session error paths already identify a failing agent by backend.