Skip to content

docs(changelog): document 0.2.119 staging rollback + root cause #82

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Number531 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs(changelog): document 0.2.119 staging rollback + root cause #82

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion super-legal-mcp-refactored/CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,13 @@ All notable changes to the Super Legal MCP Server are documented in this file.

### Upgraded — `@anthropic-ai/claude-agent-sdk` 0.2.97 → 0.2.119

Absorbs 22 point releases covering security, correctness, and observability improvements. Probe (2026-04-24) confirmed the new per-platform native binary packaging (0.2.113+) is safe with our existing `npm ci --omit=dev --ignore-scripts --legacy-peer-deps` Dockerfile command — no build changes required.
> **⚠️ Deployment status (2026-04-24 post-merge):** Code at 0.2.119 merged to `main` (PR [#79](https://github.com/Number531/Legal-API/pull/79) + doc consistency follow-up [#80](https://github.com/Number531/Legal-API/pull/80)). Staging deploy via `/deploy` **failed on first `query()` invocation** with `Claude Code native binary not found at .../claude-agent-sdk-linux-x64-musl/claude`. Root cause is an SDK runtime-lookup bug that tries the musl binary path first and fails to fall through to the glibc path when musl isn't installed — which it correctly isn't on our `node:22-slim` (Debian glibc) base. **Rolled back the staging GCE MIG to the previous instance template (0.2.97 image) — health green.** Code remains at 0.2.119 on `main` pending the Dockerfile symlink fix. Tracking: [Legal-API #81](https://github.com/Number531/Legal-API/issues/81) (internal), [anthropics/claude-agent-sdk-typescript#296](https://github.com/anthropics/claude-agent-sdk-typescript/issues/296) (upstream).
>
> **What the pre-merge probe missed.** Static analysis on 2026-04-24 correctly verified (1) platform-package tarball structure (binary pre-chmodded 0755), (2) zero postinstall scripts — `--ignore-scripts` is not blocking anything, (3) npm's `libc` filter installs the glibc variant only. What it did not verify was the SDK's runtime lookup order inside a spawned container, which probes the musl path regardless of what's actually installed. Lesson for future SDK bumps: add a minimal container-level smoke test (`docker run <image> node -e 'import(...).then(s => s.startup())'`) to the pre-merge checklist. The static/package-level analysis was correct but insufficient on its own.
>
> **Fix path.** Preferred: 5-line Dockerfile symlink addition after `npm ci` that points `claude-agent-sdk-linux-x64-musl/claude` at the glibc binary's real path. The binary is a native glibc ELF — correct for our OS; the `-musl` suffix in the lookup path is just a naming key the SDK's buggy resolution expects. Alternative: explicit `pathToClaudeCodeExecutable` option at each `agentQuery()` call site (Anthropic's own workaround pattern, per [claude-code-action#1235](https://github.com/anthropics/claude-code-action/pull/1235)) — cleaner architecturally, wider code footprint. A follow-up PR (targeted for v6.3.1) will land the symlink fix.

Absorbs 22 point releases covering security, correctness, and observability improvements. Probe (2026-04-24) confirmed the new per-platform native binary packaging (0.2.113+) is safe at the **package-install** layer with our existing `npm ci --omit=dev --ignore-scripts --legacy-peer-deps` Dockerfile command — no npm-level changes required. Runtime-level SDK lookup bug requires the Dockerfile symlink workaround noted above to make the deployed container functional.

**Key changes captured by the bump:**

Expand Down