All monitored APIs

Auth

WorkOS API breaking changes, mapped to your GitHub repos

Versionly monitors the WorkOS API (workos.com) in the Auth catalog. When WorkOS ships an OpenAPI or changelog change, we find call sites in the repositories you connect and open a reviewable auto-fix pull request.

What breaks without monitoring

  • WorkOS request or response fields can rename without a compile error
  • Auth SDK method signatures drift between WorkOS releases
  • Calls to workos.com can change auth, versioning, or payload shape

How Versionly helps

  • Catalog monitoring for WorkOS (workos.com)
  • Import and host detection for WorkOS usage in connected repos
  • File-level impact mapping and reviewable GitHub pull requests

WorkOS + Versionly — FAQ

Does Versionly auto-merge WorkOS upgrades?
No. Versionly opens a pull request when WorkOS API changes hit your connected repos. Your team reviews and merges.
How does Versionly detect WorkOS usage?
The catalog entry for WorkOS matches SDK imports, package names, and typical workos.com hosts in the repositories you choose to connect.
See the full four-step workflow

Next step

Connect one repo. Review the first pull request.

Start with the project that talks to payments or an LLM vendor. If the PR looks wrong, close it. Versionly does not merge.

Create workspaceSDK & MCP docs