Skip to content

docs: record published index-it-mcp 1.5.1 (wheel and image accepted; PMCP offline, rehearsal and browser not run) - #126

Merged
ViperJuice merged 1 commit into
mainfrom
docs/v1.5.1-published
Nov 9, 2026
Merged

ViperJuice merged 1 commit into
mainfrom
docs/v1.5.1-published

Conversation

@ViperJuice

@ViperJuice ViperJuice commented Nov 9, 2026 •

Copy link
Copy Markdown
Collaborator

This follows #123. It changes the docs that call 1.5.1 the "prepared candidate" to "published 1.5.1", recommends pip install index-it-mcp==1.5.1, and keeps the warning not to install 1.5.0 or 1.4.1 without constraining mcp below 2. It also adds the 1.5.1 delivered-acceptance record.

Status: published=true. Acceptance is partial: every delivered wheel and image check passed, but PMCP offline, rehearsal and browser were not run. deployed=false.

Published. Release Automation run 42550570039 built tag v1.5.1 from 13470d0 (tree ff36908). It published the PyPI wheel (Requires-Dist: mcp<2,>=1.27) and sdist, the GitHub release, and the signed image ghcr.io/consiliency/code-index-mcp@sha256:68da7158….

Passed (dev0, Python 3.12.14, clean worktree at 13470d0):

  • Downloads and image. The PyPI sha256 values match the recorded values and are byte-identical to the GitHub release assets. image-reference.txt names the published digest. The image was pulled anonymously by digest (labels v1.5.1 / 13470d0). cosign v2.5.2 verified the keyless signature: identity release-automation.yml@refs/heads/main, workflow sha 13470d0.
  • Release smoke. release_smoke.py --wheel-path <PyPI wheel> --wheel-sha256 f344…f9e --unconstrained --image-ref <digest> --stdio --docker-network host, with a fresh prefetched TREE_SITTER_LANGUAGE_PACK_CACHE_DIR.
    • dev0 still can't reach bridge-published container ports, so the container probe used host networking.
    • Locked wheel: STDIO and lifecycle passed.
    • Unconstrained wheel: resolved mcp 1.30.0; initialize (8 tools) and STDIO queries passed.
    • Container: cosign, HTTP before and after restart, log privacy, lifecycle and safety passed.
  • The 1.5.0 defect is fixed.
    • In a fresh Python 3.12 venv, a plain pip install index-it-mcp==1.5.1 resolves mcp 1.30.0, and pip check is clean.
    • A raw JSON-RPC probe of index-it-mcp stdio got initialize and tools/list (8 tools), and the server exited 0.
  • Co-install with phase-loop-runtime==0.7.30: uv pip check is clean, and the installed files match the wheel's RECORD.
    • Resolved: baml-bridge 0.23.0, tree-sitter 0.26.0, treesitter-chunker 6.0.0, language-pack 1.20.0, mcp 1.30.0.
    • mcp-index --version reports 1.5.1. grammars prefetch verified 47/47; grammars check found 47 offline, 0 missing.
    • With MCP_BAML_TELEMETRY unset or blank, a BAML import records nothing.
  • PMCP prepare with the PyPI wheel: registry-origin manifest bound to 13470d0, PMCP 2.7.3.

Not run:

  • PMCP offline. The 1.5.0 harness gap is still on main: scripts/v13_pmcp_pilot.py (unchanged since Require authenticated Qdrant, least-privilege workflow tokens, scoped dependency triage #109) gives its fixture a fresh XDG_CACHE_HOME with no prefetched grammar cache, so network-denied sandbox workers can't load grammars. Not fixed here.
  • PMCP rehearsal and browser. Skipped for the same reasons as 1.5.0: the same fixture, dev0's Qdrant networking (bridge publishing is broken, and in host mode gRPC port 6334 is held by the live Qdrant), and Inspector 2.6.0 plus an operator session for browser mode.

Observation: STDIO serverInfo.version reports 1.30.0, the mcp SDK version, not the package version.

Deployed: no. dev0's code-index child still runs build b79cc7c and wasn't changed.

Tests (dev0, one file per run, serial, under nice): all tests/docs files, tests/test_release_metadata.py, tests/test_v13_release_candidate.py, tests/smoke/test_release_smoke_contract.py and tests/test_workflow_release_policy.py pass. The pinning tests now require "published 1.5.1", the pip install index-it-mcp==1.5.1 recommendation and the 1.5.0/1.4.1 warning, and they reject "prepared candidate".

🤖 Generated with Claude Code


Autofix with [code]smith
Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.

v1.5.1 is published (Release Automation run 42550570039, tag v1.5.1 at
13470d0). Delivered acceptance on dev0:

- The PyPI wheel/sdist digests match the GitHub release assets. The image
  digest and its cosign keyless signature (main, workflow sha 13470d0) are
  verified.
- release_smoke.py --unconstrained --stdio --image-ref passes: locked
  wheel, unconstrained wheel (mcp 1.30.0) and container. The container
  probe used --docker-network host because dev0 still cannot reach
  bridge-published ports.
- The 1.5.0 defect is fixed. A plain `pip install index-it-mcp==1.5.1`
  resolves mcp 1.30.0, and `index-it-mcp stdio` serves initialize and
  tools/list. The co-install with phase-loop-runtime 0.7.30 passes
  `uv pip check`. Grammars and BAML telemetry checks pass.
- PMCP prepare passes. Offline is not run because the pilot fixture's
  grammar-cache gap is still on main; rehearsal and browser are skipped
  as for 1.5.0.
- dev0 still runs build b79cc7c.

Docs change "1.5.1 prepared candidate" to "published 1.5.1", recommend
`pip install index-it-mcp==1.5.1`, and keep the warning not to install
1.5.0 or 1.4.1 without constraining mcp below 2. The docs tests are
updated to match.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 9, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-09T02:54:12.822066Z 5e72123 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@ViperJuice
ViperJuice merged commit 17b9eff into main Nov 9, 2026
14 checks passed
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