[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Open
greenkeeper bot opened this issue Jan 13, 2019 · 5 comments
Open

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

greenkeeper bot opened this issue Jan 13, 2019 · 5 comments
Labels
greenkeeper

Comments

@greenkeeper
Copy link
Contributor
greenkeeper bot commented Jan 13, 2019

The devDependency ajv was updated from 6.6.2 to 6.7.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 failed (Details).
Release Notes for v6.7.0

Option useDefaults: "empty" to replace null and "" (empty strings) with default values.
Update draft-04 meta-schema to remove incorrect usage of "uri" format.

Commits

The new version differs by 17 commits.

There are 17 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴
@greenkeeper
Copy link
Contributor Author
greenkeeper bot commented Jan 13, 2019

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

@greenkeeper
Copy link
Contributor Author
greenkeeper bot commented Feb 9, 2019
  • The devDependency ajv was updated from 6.8.1 to 6.9.0.

Your tests are still failing with this version. Compare changes

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 23 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.
  • 6d4b31e 6.8.1

There are 23 commits in total.

See the full diff

@greenkeeper
Copy link
Contributor Author
greenkeeper bot commented Feb 10, 2019
  • The devDependency ajv was updated from 6.9.0 to 6.9.1.

Your tests are still failing with this version. Compare changes

@greenkeeper
Copy link
Contributor Author
greenkeeper bot commented Feb 22, 2019
  • The devDependency ajv was updated from 6.9.1 to 6.9.2.

Your tests are still failing with this version. Compare changes

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

@greenkeeper
Copy link
Contributor Author
greenkeeper bot commented Mar 3, 2019
  • The devDependency ajv was updated from 6.9.2 to 6.10.0.

Your tests are still failing with this version. Compare changes

Release Notes for v6.10.0

Option strictDefaults to report ignored defaults (#957, @not-an-aardvark)
Option strictKeywords to report unknown keywords (#781)

Commits

The new version differs by 8 commits.

  • 6c20483 6.10.0
  • 38d1acd refactor: strictDefaults option
  • e993bd6 feat: strictKeywords option to report unknown keywords, closes #781
  • 9a28689 style: fix
  • 18268c5 additional tests for strictDefault options
  • 4b76519 Merge branch 'not-an-aardvark-invalidDefaults-option'
  • 88199d5 rename option to strictDefaults
  • c081061 feat: invalidDefaults option to warn when defaults are ignored, fixes #957

See the full diff

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
greenkeeper
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
0 participants