Repository navigation
docs: prepare 2.3.0 npm release (honest positioning, tarball smoke) - #148
PatrickSys wants to merge 2 commits into
Conversation
Align README and docs with team-conventions plus edit-preflight positioning, credit Aider/Repomix/jCodeMunch, and separate shipped 2.3.0 from planned 2.4.0. Add 2.3.0 CHANGELOG release notes including the npm 2.2.0 silent CLI fix.
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![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: e823cdfcb2
ℹ️ 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".
| ## Tool Surface | ||
|
|
||
| 10 MCP tools + active/project-scoped context resources. | ||
| 10 MCP tools plus project-scoped context resources in published 2.2.0/2.3.0. **`get_code_relationships`** and related navigation improvements are documented below for the in-repo build; treat them as **2.4.0** until that release is on npm unless you install from source. |
There was a problem hiding this comment.
When 2.3.0 is published from this checkout, get_code_relationships will already be available: package.json declares version 2.3.0 and packages dist, while src/tools/index.ts unconditionally includes the tool in TOOLS and dispatches it, and src/index.ts exposes that list through MCP. There is no 2.4.0 feature gate. Labeling it as requiring 2.4.0 incorrectly tells users of the pending release that they must install from source or wait for another release. Describe it as included in pending 2.3.0, or exclude it from that release if postponement is intended.
Useful? React with 👍 / 👎.
 [Low impact] The changes affect documentation readers, not package behavior. The documentation appears safe to merge, with a non-blocking correction needed to the stated release boundaries. Findings
SummaryPrepares the documentation for the pending 2.3.0 release.
Reviews (1) · Last reviewed commit: "docs: prepare honest 2.3.0 release surfa..." · Reviewed by Greptile |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| ## Tool Surface | ||
|
|
||
| 10 MCP tools + active/project-scoped context resources. | ||
| 10 MCP tools plus project-scoped context resources in published 2.2.0/2.3.0. **`get_code_relationships`** and related navigation improvements are documented below for the in-repo build; treat them as **2.4.0** until that release is on npm unless you install from source. |
There was a problem hiding this comment.
get_code_relationships is included in the pending 2.3.0 package, not reserved for 2.4.0. The package builds and includes all of src, and TOOLS registers this tool without a version check. The same mismatch affects parsing.maxChunks and Transformers.js v4 elsewhere in the changed docs.
Match these release labels to the actual 2.3.0 package, or exclude the features from that build. Otherwise, users are told to wait for features their installed package already contains.
Knowledge Base Used: Command-line workflows
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
|
Integration branch README (after the 25.7% vs jCodeMunch sentence):
CHANGELOG 2.3.0 Docs bullet — append:
README Evidence — one sentence that the niche aggregate table is a separate frozen family (not pooled with 25.7% expected-file recovery). Also update Setup bullet to six clients (VS Code + Windsurf) if #153 merges first. Agent: cursor-cloud/cbc-integration |
Summary
Prepares codebase-context 2.3.0 for Patrick’s manual npm publish (no publish from this PR).
init, doc policy).npm pack→npx file:…tgz—--version→2.3.0,reindex --no-embeddingsoneval-controlledfixture succeeds.Release checklist (Patrick)
tests/release-truth-surfaces.test.tspasses locally)pnpm testgreen onmasterafter mergenpm packand spot-check:--version,status,reindexfrom tarballv2.3.0/ run release workflow (manual publish — do not rely on silent 2.2.0 CLI)npx -y codebase-contextpicks it up