search

fnogatz / xsd2json

Translate XML Schema into equivalent JSON Schema
MIT License
150 stars 28 forks source link

An in-range update of ajv is breaking the build 🚨 #98

Closed greenkeeper[bot] closed 5 years ago

greenkeeper[bot] commented 5 years ago

The devDependency ajv was updated from 6.8.1 to 6.9.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

ajv is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details - ❌ **continuous-integration/travis-ci/push:** The Travis CI build could not complete due to an error ([Details](https://travis-ci.org/fnogatz/xsd2json/builds/491089165?utm_source=github_status&utm_medium=notification)).
Release Notes for v6.9.0

OpenAPI keyword nullable can be any boolean (and not only true).
Custom keyword definition changes:

  • dependencies option in to require the presence of keywords in the same schema.
  • more strict validation of the definition using JSON Schema.
Commits

The new version differs by 14 commits.

  • cd404c4 6.9.0
  • 7079aed remove property in custom keyword definition schema
  • c89ca0e eslint option
  • 47c8fc9 refactor: use json schema to validate custom keyword definition
  • 33d1ac4 style fix
  • fdfbd44 feat: support for required dependencies of custom keyword (keywords that must be present in the same schema)
  • f080c91 docs: double quotes
  • 51e858e docs: clarify "format" option values
  • 0cf6e98 Merge branch 'mattpolzin-nullable-can-be-false'
  • ac2221a style fix
  • c5b9516 Merge branch 'master' into nullable-can-be-false
  • 58879a0 fix: pin jshint to 2.9.7 (#939)
  • 859259e Add tests that show that with nullable option on but 'nullable' keyword set to false an object is not nullable.
  • 28c85ad Allow nullable property of JSON Schema object to be false as well as true. Remove test that asserted failure if nullable was false.

See the full diff

FAQ and help There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

greenkeeper[bot] commented 5 years ago

After pinning to 6.8.1 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

greenkeeper[bot] commented 5 years ago

Your tests are still failing with this version. Compare changes

greenkeeper[bot] commented 5 years ago

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Commits

The new version differs by 11 commits.

  • 2aa49ae 6.9.2
  • dffe473 chore(package): update mocha to version 6.0.0 (#952)
  • 6831b68 feat: extract method to validate custom keyword definition
  • 187e021 fix: removeAdditional option breaking custom keywords, closes #955, closes epoberezkin/ajv-keywords#91
  • f6d25de Replace single quotes with double quotes to get build scripts running on Windows (#946)
  • c52f2e1 update package.json scripts
  • 098df6d test: enable browser tests in node 10
  • 8720547 skip browser tests
  • a7f78f2 refactor: split issues.spec.js file
  • 71dc5dc refactor: split options.spec.js file
  • 51685b8 chore(package): update nyc to version 13.2.0 (#930)

See the full diff