Skip to content

chore(acp): bump dimcode and grok registry pins to probed versions - #1030

Merged
kaizhou-lab merged 1 commit into
mainfrom
chore/acp-lock-sync-20261015
Oct 14, 2026
Merged

kaizhou-lab merged 1 commit into
mainfrom
chore/acp-lock-sync-20261015

Conversation

@kaizhou-lab

Copy link
Copy Markdown
Contributor

Registry snapshot

Version drift

backend package old new
dimcode dimcode 0.5.17 0.5.18
grok @xai-official/grok 1.0.57 1.0.58

The other Registry-pinned entries (autohand, codebuddy, deepagents, dirac, glm-acp-agent, kilo, minimax-code, nova, pi, sigit) match the snapshot. mimo-code is a non-Registry builtin and is excluded from drift reconciliation.

Probe evidence

Each package was probed serially at the exact new version with the Registry's declared argv, no inherited HOME and no credentials. Both completed ACP initialize at protocolVersion 1.

backend probed argv session/new classification
dimcode npx -y dimcode@0.5.18 acp -32000 "Authentication required: Provider credentials are required" auth required
grok npx -y @xai-official/grok@1.0.58 agent stdio -32000 "Authentication required", data "no auth method id provided" auth required

Drifted but not upgraded: none.

Structural diff

The previous snapshot (v2026.10.14-2bb9475) was fetched from its versioned CDN path and diffed per agent. For both npx entries above, args and env are byte-identical. The only other changes are binary artifacts for antigravity-acp and kimchi, neither of which AionCore pins. No distribution type was added or removed for any pinned backend.

Scope

Lock-only. A fixed-string scan (grep -rnF) for each outgoing version across crates/**/*.rs returned no match, so no lock-derived test assertion needed updating. The version literals in npx_cache_repair.rs are cache-path hash fixtures and are deliberately untouched.

Validation

  • just migration-check: passed.
  • just lint-fix (cargo fix + clippy --fix --workspace -D warnings): clean, no fixes produced.
  • just fmt: clean.
  • just _auto-commit-fixes: nothing to commit.
  • Local cargo nextest run --workspace skipped by standing policy for a lock-only bump; the Test check on this PR is the authority.

Logging

No logging change. This is a resource-manifest version bump on an existing, already-instrumented spawn path.

Registry snapshot v2026.10.14-5f08813 declares newer npx packages for two
pinned builtin agents. Each new version was probed locally before the pin
moved: ACP initialize succeeded for both, and session/new returned a cleanly
classified authentication requirement.

- dimcode 0.5.17 -> 0.5.18
- grok 1.0.57 -> 1.0.58

No lock-derived test assertion embeds either outgoing version, so the
release lock manifest is the only file that changes.
@kaizhou-lab
kaizhou-lab merged commit 503a871 into main Oct 14, 2026
6 checks passed
@kaizhou-lab
kaizhou-lab deleted the chore/acp-lock-sync-20261015 branch October 14, 2026 17:26
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