Repository navigation
chore(deps): update oasdiff/oasdiff-action action to v0.1.22 - #34
Merged
Merged
Conversation
Contributor
Test results 204 files 204 suites 1m 22s ⏱️ Results for commit 26590c2. |
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.
This PR contains the following updates:
v0.1.21→v0.1.22Release Notes
oasdiff/oasdiff-action
v0.1.22Compare Source
Highlights
Upgraded to oasdiff v1.36.0
Every action now runs
tufin/oasdiff:v1.36.0(#211). What a workflow author sees:jq .if your specs are generated.deprecatedline rather than thex-sunsetdate they complain about, and a parameter's deprecation finding looked fordeprecatedin the parameter's schema, so it landed on the operation line or carried no line at all.allOfbranch to a request is an error again, onrequest-body-all-of-addedandrequest-property-all-of-added. Both were reported as warnings with a comment suggesting another branch might still keep a constraint that was dropped, which cannot happen: adding a branch only narrows what a request may send. A job that fails on error will now fail on these.allOf,anyOforoneOfbranch. The branch name no longer ends in a separator, and the name is part of the fingerprint, so a stored approval for one of these changes is requested once more.validatereturns its findings in the same order every run, sorted by file, line and column, so a step that compares stored reports stops seeing a reshuffle on every push. A spec withcallbackscan also report findings it did not before, andmultiple-of-not-positiveis nowschema-multiple-of-not-positive.diffaction takes--exclude-elements tags, which drops tag changes fromdiffandsummary, both the tags an operation is listed under and the document's own tag definitions.Also in the image: git revisions work on a repository mounted from the host, so the
rev:pathsyntax no longer fails with "detected dubious ownership" on a self-hosted runner.Full Changelog: oasdiff/oasdiff-action@v0.1.21...v0.1.22
Configuration
📅 Schedule: (in timezone Europe/Berlin)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.