API changelogs
For repository-backed collections, Elva uses available Git history to show API-related changes with author and timestamp information.
A completed repository scan associates available history with files backing discovered endpoints. The resulting feed depends on the history and source files available to that scan.
Rebuilt from git on every scan
Open a repository-backed collection's changelog to review recent entries and their affected endpoints. Use the source references to inspect the underlying change.
Example: review a changed order response
A changelog entry shows a change to the file defining GET /orders/{orderId}. Open the associated source change and compare the response schema with your consumers' expectations. If a field was renamed, review affected contracts for drift and decide how to communicate and release the change.
A source-derived changelog is evidence about code changes, not confirmation that a contract or MCP deployment was published. Verify contract version history and destination results separately. Imported specifications without repository history may not have the same source-derived feed.
On this page
- API changelogs