Update dependency swagger-parser to v10 #8
Closed
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:
3.4.2
->10.0.3
Release Notes
APIDevTools/swagger-parser
v10.0.3
Compare Source
v10.0.2
Compare Source
v10.0.1
Compare Source
v10.0.0
Compare Source
Breaking Changes
YAML
export. We recommend using@stoplight/yaml
insteadOther Changes
continueOnError
option that allows you to get all errors rather than just the first oneFull Changelog
v9.0.1
Compare Source
v9.0.0
Compare Source
Moved Swagger Parser to the @APIDevTools scope on NPM
The "swagger-parser" NPM package is now just a wrapper around the scoped "@apidevtools/swagger-parser" package
Full Changelog
v8.0.4
Compare Source
v8.0.3
Compare Source
v8.0.2
Compare Source
v8.0.1
Compare Source
v8.0.0
Compare Source
Potentially Breaking Changes
validate()
function now uses the official JSON Schemas for Swagger 2.0 and OpenAPI 3.0 schema validation. We tested this change on over 1,500 real-world APIs and there were no breaking changes, but we're bumped the major version number just to be safe.Full Changelog
v7.0.1
Compare Source
v7.0.0
Compare Source
Breaking Changes
Dropped support for Node 6
Updated all code to ES6+ syntax (async/await, template literals, arrow functions, etc.)
No longer including a pre-built bundle in the package. such as Webpack, Rollup, Parcel, or Browserify to include Swagger Parser in your app
Other Changes
Full Changelog
v6.0.5
Compare Source
v6.0.3
Compare Source
v6.0.2
Compare Source
v6.0.1
Compare Source
v6.0.0
Compare Source
Dropped support for Bower, since it has been deprecated
Removed the
debug
dependencyFull Changelog
v5.0.6
Compare Source
v5.0.5
Compare Source
v5.0.4
Compare Source
v5.0.2
Compare Source
v5.0.1
Compare Source
v5.0.0
Compare Source
Full Changelog
v4.1.0
Compare Source
validate()
method. It will now detect when a JSON Schema in your API definition hasrequired
properties that don't exist.Full Changelog
v4.0.2
Compare Source
v4.0.1
Compare Source
v4.0.0
Compare Source
Breaking Changes
Update the Swagger 2.0 JSON schema, so it's possible that an API that previously passed validation may no longer pass due to changes in the Swagger schema
To reduce the size of this library, it no longer includes polyfills for Promises and TypedArrays, which are natively supported in the latest versions of Node and web browsers. If you need to support older browsers (such as IE9), then just use this
Promise
polyfill and thisTypedArray
polyfill.Minor Changes
validate()
method andx-
vendor extensionsFull Changelog
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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 has been generated by Mend Renovate. View repository job log here.