Versioning & disclosure
If you build on the PorchOps developer surface, these are the commitments you can rely on: how versions change, how long deprecated versions keep working, and how to report a security issue.
Versioning
Both OpenPlaybook and the MCP tool surface version with semantic versioning. What each bump means:
- Major: a breaking change. A document or client written for the old major may stop validating. Major bumps are rare and announced.
- Minor: backward-compatible additions. New fields, new tools, new step or trigger kinds. Existing documents and clients keep working.
- Patch: corrections to the spec text or bug fixes with no wire-shape change.
Deprecation window
When a new major version ships, the runtime continues to support the prior major version for 12 months. That window is your migration runway: a playbook or integration pinned to the old major keeps running for a year after the successor lands. The window mirrors the MCP specification's own 12-month deprecation policy.
Security disclosure
Report a security issue privately to security@porchops.com. Please do not open a public issue for a vulnerability. Include enough detail to reproduce; we acknowledge reports and keep you posted through remediation.
Status & changelog
The developer surface rides the same operational and release surfaces as the rest of PorchOps:
- Status: current operational state and incident history are on the public status page. Your BYOA client can also read status directly via the code-context server (v1.5).
- Changelog: what shipped, including developer-surface changes, is on the public changelog.
- Spec history: the OpenPlaybook changelog and RFC process live in the public spec repository.