docs: mark PyPI distribution gap as shipped (1.6.0)#22
Conversation
…plan ROADMAP M9 release notes now reflect tag-triggered PyPI publish via Trusted Publishing; PRODUCT_UPGRADE_PLAN weakness table marks the GitHub-only distribution gap as resolved (pip/pipx shipped; uvx/Homebrew still pending). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 8f82e1aa20
ℹ️ 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".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| `pip install codebase-index` -> `init` -> `index` -> ask a question is verified end-to-end by | ||
| `scripts/release_smoke.py`.* |
There was a problem hiding this comment.
This overstates the release verification: scripts/release_smoke.py builds the local wheel and installs it with pip install <wheel path>, so it never exercises resolving or installing codebase-index from PyPI. For the PyPI-shipped path, this could let a missing/broken PyPI publication pass the documented smoke gate; either describe this as a local-wheel smoke or add a post-publish pip install codebase-index check.
Useful? React with 👍 / 👎.
1 participant
Follow-up to #20/#21 — updates the planning docs to reflect PyPI is now shipped.
pip install codebase-index.uvx/Homebrew noted as still pending.The plugin-bootstrap note (
requirements.locktarball pin, "not PyPI") is left as-is — it accurately describes the plugin's isolated-venv bootstrap, which is unchanged.🤖 Generated with Claude Code