Defining the API lifecycle in a modular, reusable, and machine readable way that can help others learn about what the API lifecycle could be, as as define their own evolving API lifecycle.
How do you evaluate a breaking change using the GitHub API, pulling the latest OpenAPI, but then pulling that last version and doing a diff. Clearly has to be some sort of known approach to where OpenAPI is located as well as the version branches, but seems like it could be defined, and then turned into a test as a collection.
How do you evaluate a breaking change using the GitHub API, pulling the latest OpenAPI, but then pulling that last version and doing a diff. Clearly has to be some sort of known approach to where OpenAPI is located as well as the version branches, but seems like it could be defined, and then turned into a test as a collection.