chore(acp): bump codebuddy, dimcode, glm and grok registry pins to probed versions - #960
Merged
Merged
Conversation
kaizhou-lab
added a commit
that referenced
this pull request
Sep 2, 2026
…ons (#963) ## Summary Scheduled ACP Registry version sync. Three npx pins drifted since #960, each backed by a fresh serial ACP probe of the exact pinned version. This one is a single-file diff: no lock-derived test assertion embeds any of the three versions, and codebuddy — the only package whose version appears in a test — did not drift. | backend | package | old → new | initialize | session/new | |---|---|---|---|---| | dimcode | `dimcode` | 0.3.26 → **0.3.27** | ok (agentInfo version 0.3.27) | auth required (`-32000`, "Provider credentials are required") | | grok | `@xai-official/grok` | 1.0.16 → **1.0.17** | ok (protocolVersion 1) | auth required (`-32000`, "no auth method id provided") | | kilo | `@kilocode/cli` | 7.5.6 → **7.5.9** | ok (agentInfo Kilo 7.5.9) | **succeeded** unauthenticated | All three 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. kilo opened a session advertising model, thought_level, and mode options; that catalog is evidence only and is not persisted (skill step 11 leaves those columns to the runtime). dimcode still self-reports `agentInfo.title` as "DimAgent" against a public listing of "DimCode" — a standing vendor quirk, not an AionCore defect. **Snapshot diff beyond the lock:** a per-agent comparison of the raw CDN JSON against the previous snapshot shows every change is version churn — no distribution type was added or removed, and no entrypoint args or env changed for any of the 39 agents. Twelve non-lock agents also moved (claude-acp 0.73.0, cline 3.0.61, codex-acp 1.8.0, gemini-cli 0.58.0, factory-droid, plus binary artifacts for cursor, devin, harn, junie, kimi, opencode, and kilo's own binary channel). None of them is in our release lock, so all are report-only here; binary distributions in particular stay out of scope per the drift workflow's separate treatment of platform artifacts. **Derived-assertion scan:** all three outgoing versions (`0.3.26`, `1.0.16`, `7.5.6`) were scanned across `crates/**/*.rs` with fixed-string matching before staging, and none has a single hit. `registry_npx_lock.rs` still pins codebuddy at `2.143.0`, which is correct — codebuddy is unchanged in this snapshot. `npx_cache_repair.rs` keeps its own version literals: those are cache-path hash fixtures, not lock assertions. The other 8 Registry-pinned packages (autohand, codebuddy, deepagents, dirac, glm-acp-agent, 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.09.02-fa32608`](https://cdn.agentclientprotocol.com/registry/v1/v2026.09.02-fa32608/registry.json) of `agentclientprotocol/registry`, fetched via the versioned CDN path for reproducibility. - 39 ids in the raw 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: this is a lock version bump only; 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
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. Four npx pins drifted since #957, 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,data.category: auth)dimcode-32000, "Provider credentials are required")glm-acp-agent@xai-official/grok-32000, "no auth method id provided")All four meet the release-lock criterion:
initializesucceeds, andsession/neweither succeeds or returns a clearly classified authentication requirement. Probes ran serially with no inherited HOME or credentials.glm-acp-agent crosses another minor (1.7.0 → 1.8.0), so its entrypoint was exercised rather than assumed: the Registry distribution still declares a bare
glm-acp-agentcall with no arguments, and that exact invocation completedinitializeand opened a session advertising thought_level, mode, and model options. It still self-reportsagentInfo.versionas1.0.0, and dimcode still reportsagentInfo.title"DimAgent" against a public listing of "DimCode" — both standing vendor quirks, not AionCore defects. No session catalog is persisted (skill step 11 leaves those columns to the runtime).Snapshot diff beyond the lock: comparing the raw CDN JSON against the previous snapshot, every change is version churn with no structural movement — no distribution type was added or removed, and no entrypoint args or env changed for any of the 39 agents. Two binary distributions moved (
cursorto lab build 2026.08.25-3e8eec8,harnto v0.10.125 with a new sha256) andfactory-droid's npx package moved to 0.209.0; none of the three is in our release lock, so all are report-only here per the drift workflow's separate treatment of binary distributions.Derived assertion updated:
registry_npx_lock.rspins codebuddy's exact version inside a--package-form argument list, so it moves with the lock —2.142.0→2.143.0. All four outgoing versions were scanned acrosscrates/**/*.rsbefore staging, using fixed-string matching; codebuddy's is the only real assertion and the other three have no hits at all.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 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-coderemains the one non-Registry builtin (noregistry_json_id), excluded from drift reconciliation.Registry snapshot
v2026.09.01-fca7bdfofagentclientprotocol/registry, fetched via the versioned CDN path for reproducibility.antigravity-acpremains listed and deferred as binary-only since 2026-08-21;fast-agentandminion-coderemain listed but uvx-only and therefore out of scope.)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.