Skip to content

chore(master): release 2.4.0 #448

chore(master): release 2.4.0

chore(master): release 2.4.0 #448

Triggered via pull request October 6, 2026 14:05
Status Failure
Total duration 1m 5s
Artifacts –

test.yml

on: pull_request
Quality Checks
47s
Quality Checks
Functional Tests
1m 2s
Functional Tests
Fit to window
Zoom out
Zoom in

Annotations

3 errors, 12 warnings, and 2 notices
Functional Tests
Process completed with exit code 1.
tests/release-truth-surfaces.test.ts > release truth surfaces > keeps the manual publish fallback aligned to the package version: tests/release-truth-surfaces.test.ts#L118
AssertionError: expected '# Publishes to npm when a GitHub rele…' to contain 'description: \'Tag to publish (e.g. v…' - Expected + Received - description: 'Tag to publish (e.g. v2.4.0)' + # Publishes to npm when a GitHub release is created (or on manual run for a given tag). + # Use when release-please didn't run publish (e.g. manual release or "chore: release" merge). + name: Publish to npm on release + + on: + release: + types: [published] + workflow_dispatch: + inputs: + tag: + description: 'Tag to publish (e.g. v2.3.0)' + required: true + default: 'v2.3.0' + + permissions: + contents: read + id-token: write + + jobs: + publish: + name: Publish to npm + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v4 + with: + ref: ${{ github.event.inputs.tag || github.event.release.tag_name }} + + - uses: pnpm/action-setup@v2 + with: + version: 10 + + - uses: actions/setup-node@v4 + with: + node-version: '24' + registry-url: 'https://registry.npmjs.org' + cache: 'pnpm' + + - run: pnpm install --frozen-lockfile + + - name: Check if version already published + id: check + run: | + VERSION="$(node -e "console.log(JSON.parse(require('fs').readFileSync('package.json','utf8')).version)")" + if npm view "codebase-context@${VERSION}" version 2>/dev/null; then + echo "already_published=true" >> "$GITHUB_OUTPUT" + else + echo "already_published=false" >> "$GITHUB_OUTPUT" + fi + + - name: Quality gates + if: steps.check.outputs.already_published != 'true' + run: | + pnpm lint + pnpm format:check + pnpm type-check + pnpm build + pnpm test + + - name: Publish to npm with provenance + if: steps.check.outputs.already_published != 'true' + run: pnpm publish --access public --no-git-checks --provenance + ❯ tests/release-truth-surfaces.test.ts:118:22
tests/mcp-client-templates.test.ts > docs/client-setup.md multi-project guidance > separates process-local routing proof from native and HTTP acceptance: tests/mcp-client-templates.test.ts#L178
AssertionError: expected '# Client Setup\n\nCodebase Context ru…' to contain 'stdio process-local selection does no…' - Expected + Received - stdio process-local selection does not establish concurrent HTTP isolation + # Client Setup + + Codebase Context runs as a local MCP server: a tool your AI editor or command-line client can call while it works. Register it without a fixed folder, then let the agent supply its current repository through the `project` tool parameter. These recipes target published npm `2.4.0`. + + Use Node.js 22 or newer for these recipes. The package declares Node 18+, but native dependency requirements are narrower than that broad declaration; these checks do not establish Node 18.0 compatibility. + + The copyable registration commands target PowerShell or a POSIX terminal. Windows Command Prompt was not tested; OpenCode's quoted separator is shell-dependent. + + ## Current published-package recipes (updated 2026-10-06) + + Claude Code, Codex CLI and OpenCode registration commands were checked again on October 6 without a project argument. The other clients retain their older config-shape evidence; no-folder native agent use is unverified for them. See the dated notes below. + + Each client section says how far its isolated Windows check went: + + | Status | What it means | + | ------------------------------ | ------------------------------------------------------------------------------------------ | + | **Connected locally** | The isolated client started and connected to the server. | + | **Config recognized locally** | The isolated client found the config but still required approval before loading it. | + | **Config written locally** | The isolated command wrote the expected config. A live agent session was not claimed. | + | **Official instructions only** | The config follows current official docs, but this client was not fully exercised locally. | + + These checks cover setup and startup state. They do not measure how an agent handles a coding task. + + After registration, start a new agent session in your project and ask: + + > Use Codebase Context to find [feature] in this repository. Pass this repository's absolute path as project when checking get_indexing_status and searching. Wait for indexing if needed, read codebase://context, then search_codebase and open a returned source file. Show me the relevant files. + + The first index may take a while and download a local model. You can prepare it separately with `npx -y codebase-context@2.4.0 reindex` from the project folder. Index readiness, client connection and useful agent behavior are separate checks. + + ## Claude Code + + **Status:** Connected locally + + **Checked:** 2026-10-06 with Claude Code 2.1.291 + + **Scope:** User scope makes the registration available across projects. The agent selects the repository in tool calls. + + User setup: + + ```bash + claude mcp add --scope user --transport stdio codebase-context -- npx -y codebase-context@2.4.0 + ``` + + Optional shared project setup: + + ```bash + claude mcp add --scope project --transport stdio codebase-context -- npx -y codebase-context@2.4.0 + ``` + + `--scope project` writes shared `.mcp.json` and requires project-server approval. `--scope local` instead stores a private association for the current project in `~/.claude.json`; it does not write `.mcp.json`. + + **What was checked:** With isolated user configuration, the no-folder user command wrote the expected stdio arguments and `claude mcp get` reported Connected. + + **Limit:** Connection proof does not establish an agent investigation. The optional shared-project variant follows the official scope contract; it was not exercised in this October check. + + **Official docs:** https://code.claude.com/docs/en/mcp + + ## Codex CLI + + **Status:** Config written locally + + **Checked:** 2026-10-06 with Codex CLI 0.160.0 + + **Scope:** The command writes user config
Quality Checks
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@v2. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Quality Checks: src/cli-formatters.ts#L395
Unexpected console statement. Only these console methods are allowed: warn, error
Quality Checks: src/cli-formatters.ts#L394
Unexpected console statement. Only these console methods are allowed: warn, error
Quality Checks: src/cli-formatters.ts#L377
Unexpected console statement. Only these console methods are allowed: warn, error
Quality Checks: src/cli-formatters.ts#L376
Unexpected console statement. Only these console methods are allowed: warn, error
Quality Checks: src/cli-formatters.ts#L373
Unexpected console statement. Only these console methods are allowed: warn, error
Quality Checks: src/cli-formatters.ts#L371
Unexpected console statement. Only these console methods are allowed: warn, error
Quality Checks: src/cli-formatters.ts#L367
Unexpected console statement. Only these console methods are allowed: warn, error
Quality Checks: src/cli-formatters.ts#L280
Unexpected console statement. Only these console methods are allowed: warn, error
Quality Checks: src/cli-formatters.ts#L278
Unexpected console statement. Only these console methods are allowed: warn, error
Quality Checks: src/cli-formatters.ts#L276
Unexpected console statement. Only these console methods are allowed: warn, error
Functional Tests
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@v2. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Quality Checks
"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"
Functional Tests
"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"