All monitored APIs
Feature flags
Statsig API breaking changes, mapped to your GitHub repos
Versionly monitors the Statsig API (statsig.com) in the Feature flags catalog. When Statsig 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
- Statsig request or response fields can rename without a compile error
- Feature flags SDK method signatures drift between Statsig releases
- Calls to statsig.com can change auth, versioning, or payload shape
How Versionly helps
- Catalog monitoring for Statsig (statsig.com)
- Import and host detection for Statsig usage in connected repos
- File-level impact mapping and reviewable GitHub pull requests
Statsig + Versionly — FAQ
- Does Versionly auto-merge Statsig upgrades?
- No. Versionly opens a pull request when Statsig API changes hit your connected repos. Your team reviews and merges.
- How does Versionly detect Statsig usage?
- The catalog entry for Statsig matches SDK imports, package names, and typical statsig.com hosts in the repositories you choose to connect.
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.