Repository navigation
chore(acp): bump dimcode and grok registry pins to probed versions - #1030
Merged
Merged
Conversation
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.
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.
Registry snapshot
v2026.10.14-5f08813v2026.10.14-2bb9475).Version drift
dimcode@xai-official/grokThe other Registry-pinned entries (autohand, codebuddy, deepagents, dirac, glm-acp-agent, kilo, minimax-code, nova, pi, sigit) match the snapshot.
mimo-codeis 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
initializeatprotocolVersion 1.session/newnpx -y dimcode@0.5.18 acp-32000"Authentication required: Provider credentials are required"npx -y @xai-official/grok@1.0.58 agent stdio-32000"Authentication required", data "no auth method id provided"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,argsandenvare 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 acrosscrates/**/*.rsreturned no match, so no lock-derived test assertion needed updating. The version literals innpx_cache_repair.rsare 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.cargo nextest run --workspaceskipped 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.