Connector Versioning

Platform teams managing integrations at scale need to know exactly what connector version each customer is running, control when updates roll out, and maintain a stable production environment while iterating in staging. Connector Versioning brings full semantic versioning, per-config pinning, and immutable pushes to StackOne — giving teams the same release discipline they apply to their own software.

What’s new

• Semver for connectors - Connectors declare info.version: 1.0.0 in their YAML. Full MAJOR.MINOR.PATCH semantics apply — major bumps signal breaking changes to authentication, response shape, or action signatures
• Per-config version pinning - Pin any integration config to a specific version, Latest StackOne, or Latest custom via the Dashboard or API. Enables parallel prod/test within the same project: “Production Workday” stays on 1.2.0 while “Sandbox Workday” tests 1.3.0
• Immutable pushes - stackone push rejects duplicate version numbers by default. Any change requires a new version number. Toggle in Project Settings → Danger Zone
• Version metadata on every response - resolvedVersion, isPinned, isLegacy, isCustom, and owner are now returned on all /integrations and /accounts responses
• Custom connector isolation - Custom versions are project-scoped and take precedence over StackOne versions with the same key. Existing auth configs are auto-pinned to the current StackOne version on first custom push

Read the Connector Versioning docs