v0.3.2

[ajshedivy]

IBM i MCP Server v0.3.2

Overview

• Connection Pool Timeouts — Configure idle connection cleanup and per-query timeouts to prevent resource leaks and runaway queries
• Container Deployment Guide — New documentation for running the MCP server in Docker, Podman, and OpenShift containers

---

New Features

Connection Pool Timeouts

Control how long idle connections stay in the pool and set a maximum execution time for individual queries. This prevents connection leaks from abandoned sessions and protects against long-running queries consuming pool resources.

IBMI_POOL_IDLE_TIMEOUT_MS=60000    # Close connections idle for 60s (default: 30s)
IBMI_POOL_QUERY_TIMEOUT_MS=30000   # Kill queries running longer than 30s (default: none)

Reference: #121

---

Improvements

• Container deployment documentation covering Docker, Podman, and OpenShift with multi-architecture image support (#116)

---

What's Changed

• add instructions to run mcp server in a container by @william-xiang in add instructions to run mcp server in a container #116
• feat(pool): add connection pool idle timeout and query timeout by @ajshedivy in feat(pool): add connection pool idle timeout and query timeout #121
• refactor(pool): simplify connection pool timeout code by @ajshedivy in refactor(pool): simplify connection pool timeout code #123

Full Changelog: v0.3.1...v0.3.2

---

This discussion was created from the release v0.3.2.