chore(contracts): update Viper OpenAPI pin#225
Open
github-actions[bot] wants to merge 1 commit into
Open
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.
Scheduled drift check detected a change in the live Viper OpenAPI spec.
Source: https://viper-xi.vercel.app/api/openapi.json
oasdiff exit code: 0 (1 = breaking changes for assets-processIntegrationCreate)
oasdiff output:
Automated by contracts.yml drift job.
Summary by cubic
Sync
contracts/viper/openapi.jsonwith the latest live Viper OpenAPI spec to keep the contract pin current. No endpoint or schema changes detected; no breaking changes or consumer impact.Written for commit 19f1d53. Summary will update on new commits.