Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A generated client copy from updated openapi definition: https://api.incident.io/v1/openapiV3.json
No AI slop here. Simply updated the endpoint of the openapi definition and executed
I also removed the incident_io_openapi.json because the new one includes examples of token values and github identifies it as a secret leak, thus blocking the push. Also gitguardian would fail the same way.
Client currently fails retrieving catalog types because incidentio introduced a new
incident-templateenum value to the icon response property in GET /v2/catalog_entries, GET /v2/catalog_entries/{id} and 14 more. see the changelog here: https://docs.incident.io/api-reference/changelog#27-august-2026