Repository navigation
chore(release): prepare MCP 3.6.0 and remote plugin 0.1.2 - #180
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configuration
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Reviewed all npm, MCP registry, manifest and npx version references at 3.6.0, remote plugin metadata at 0.1.2, and the stalled-upstream fixture cleanup order. Cleanup now closes the listening server before terminating sockets, retaining the original timeout/cancellation assertion. All 659 tests pass against isolated PostgreSQL 15; shared TypeScript check, build, packaged protocol smoke, metadata verification and all current CI gates pass. Runtime changes were reviewed in merged #174/#175/#178/#166. |
Prepare MCP 3.6.0 with futures settlement history, marine port/history workflows, weekend observation-age display, and demo attribution from the merged release. Align all npm/MCP manifests and pinned npx configuration. Bump the remote plugin to 0.1.2 for durable PostgreSQL OAuth connections, which survive future process restarts.
Validation: all 659 tests pass against isolated PostgreSQL 15, release metadata, TypeScript build, and packed CLI/protocol smoke. The stalled-upstream fixture now stops accepting sockets before closing them, preventing an Undici reconnect from hanging test cleanup; the abort assertion remains unchanged. PostgreSQL persistence, restart, revocation and concurrency tests also pass on merged #174 CI. Publication will use the protected-main npm/MCP registry workflow; the remote app will use a reviewed immutable Docker image with its prepared database and backed-up encryption key.