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