Skip to content

v0.7.4 - 2026-07-31

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 31 Jul 20:26
v0.7.4
b728c2c

Release Notes

Added

  • /register/tools responses now include warnings: tools that registered in a degraded form, with the reason. A tool whose JSON Schema our codegen cannot express is registered with a permissive any signature so it stays callable; previously that only reached the server logs, invisible to a client talking to a remotely deployed session server.

Changed

  • Moved full MCP tool call / callback inputs and outputs, and execute_typescript/execute_bash code and output, from INFO to DEBUG logs to declutter traces. Added DEBUG logs describing tool result shape (structured content, JSON parse success/fallback).
  • Breaking (pctx_code_mode crate): CodeMode::with_callbacks returns (Self, CallbackReport) instead of Result<Self>, so builder-style callers see which tools failed or degraded. Per-tool isolation means the batch itself cannot fail, so the report is the only outcome.
  • Breaking (pctx_code_mode crate): CodeMode::add_callback returns Result<Vec<String>> — the reasons that tool's types were degraded to any, empty when fully typed.

Fixed

  • -v/-vv flags apply globally (previously was only applied to pctx mcp <sub-cmd> commands)
  • ExecuteBashOutput's Display printed stdout in the # STDERR section, so bash stderr was never shown. (#141)
  • /register/tools no longer fails the whole batch when a single tool cannot be registered. Each tool is registered independently: a genuinely bad tool (name clash, unparseable schema) is skipped and returned in the response's failed list, and a tool our codegen cannot type degrades to an any signature rather than being dropped. Previously one bad tool from an upstream server — such as a recursive $ref in a federated schema — took down registration for the entire batch, forcing clients into ~135 sequential per-tool calls per session.
  • Declared rmcp minimum raised from 1.2.0 to 1.8.0, the version the code actually requires. With the understated minimum, downstream consumers of the git-dep crates could resolve an older rmcp and fail to compile pctx_session_server.

Install pctx 0.7.4

Install prebuilt binaries via shell script

curl --proto '=https' --tlsv1.2 -LsSf https://github.com/portofcontext/pctx/releases/download/v0.7.4/pctx-installer.sh | sh

Install prebuilt binaries via Homebrew

brew install portofcontext/tap/pctx

Install prebuilt binaries into your npm project

npm install @portofcontext/pctx@0.7.4

Download pctx 0.7.4

File Platform Checksum
pctx-aarch64-apple-darwin.tar.gz Apple Silicon macOS checksum
pctx-x86_64-pc-windows-msvc.zip x64 Windows checksum
pctx-aarch64-unknown-linux-gnu.tar.gz ARM64 Linux checksum
pctx-x86_64-unknown-linux-gnu.tar.gz x64 Linux checksum

Verifying GitHub Artifact Attestations

The artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI:

gh attestation verify <file-path of downloaded artifact> --repo portofcontext/pctx

You can also download the attestation from GitHub and verify against that directly:

gh attestation verify <file-path of downloaded artifact> --bundle <file-path of downloaded attestation>
Assets 21
Loading