Skip to content

Upgrade

The project is pre-1.0. Public contracts (configuration schema, tool inputs/outputs, capability names) may change between releases until v1.

Supported versions

Per SECURITY.md:

  • Fixes target the latest release and main only.
  • Pre-1.0 releases do not guarantee backward-compatible configuration or tool schemas.

Upgrade path

Binary

  1. Read the GitHub Release notes for breaking changes.
  2. Verify cosign signature and checksums (RELEASE.md).
  3. Replace the binary; restart MCP hosts pointing at the new path.
  4. Re-run local gates if you build from source: task check.

Container

  1. Pin by digest or semver tag: ghcr.io/platformrelay/ibm-mq-mcp:<version>.
  2. Verify image signature before deploy (RELEASE.md).
  3. Rolling restart — no in-place migration tool is provided.
  4. When profiles exist, validate configuration against the release notes before cutover (Configuration — schema TBD).

Configuration and policy migrations

No automated migration tooling is planned for v0. When ADR-0003 and ADR-0004 fix schemas, upgrade notes will call out renames explicitly in release changelogs (generated by git-cliff from conventional commits).

MCP clients

Update MCP host configuration if tool names or required arguments change. The tool reference will be generated or CI-checked once schemas exist.

Downgrade

Not supported officially. Older releases may lack security fixes.