d-band / koa-mapper

A better and smart router middleware for koa.
40 stars 1 forks source link

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

Closed greenkeeper[bot] closed 4 years ago

greenkeeper[bot] commented 5 years ago

The dependency ajv was updated from 6.10.0 to 6.10.1.

🚨 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 direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details - βœ… **coverage/coveralls:** First build on greenkeeper/ajv-6.10.1 at 100.0% ([Details](https://coveralls.io/builds/24406416)). - ❌ **continuous-integration/travis-ci/push:** The Travis CI build failed ([Details](https://travis-ci.org/d-band/koa-mapper/builds/555083357?utm_source=github_status&utm_medium=notification)).

Commits

The new version differs by 12 commits.

  • 8b59052 6.10.1
  • 66c2907 chore(package): update del-cli to version 2.0.0 (#1014)
  • d476534 chore(package): update eslint to version 6.0.0 (#1030)
  • c468632 test: update node.js versions for travis test
  • 3ca7571 chore: update jshint
  • 120d746 chore(package): update nyc to version 14.0.0 (#994)
  • c3093bb Add "empty" to useDefaults Option type definition (#1020)
  • ab841b4 fix: addKeyword and schema without ID, closes #1001
  • bc993de chore(package): update karma to version 4.0.1 (#959)
  • 6be5ff6 fix(types): add strictKeywords to Options interface (#975)
  • 78a9403 update JSON-Schema-Test-Suite
  • d107207 Fix wrong json schema reference (#961)

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.10.0 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 passing again with this update. Explicitly upgrade to this version πŸš€

Release Notes for v6.10.2

Fix: the unknown keywords were ignored with the option strictKeywords: true (instead of failing compilation) in some sub-schemas (e.g. anyOf), when the sub-schema didn't have known keywords.

Commits

The new version differs by 8 commits.

  • 6e4a346 6.10.2
  • 53b5682 fix: the unknown keyword in the schema without known keywords inside compound schema (e.g. anyOf) is ignored with strictKeywords option
  • 669bf96 readme: fix link
  • d289c38 Tidelift subscription
  • 69802d2 security contact
  • d9d6fba Create FUNDING.yml
  • 482d2c5 labels config
  • dd827d1 label comments (for labelcious)

See the full diff