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.

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

Already on GitHub? Sign in to your account

Update ajv-keywords to the latest version 馃殌 #13188

Merged
merged 2 commits into from
Jan 31, 2018

Conversation

greenkeeper[bot]
Copy link
Contributor

@greenkeeper greenkeeper bot commented Jan 31, 2018

Version 3.1.0 of ajv-keywords was just published.

Dependency ajv-keywords
Current Version 2.1.1
Type devDependency

The version 3.1.0 is not covered by your current version range.

If you don鈥檛 accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

It might be worth looking into these changes and trying to get this project onto the latest version of ajv-keywords.

If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don鈥檛 have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.


Commits

The new version differs by 12 commits.

  • 5f9eccc 3.1.0
  • d592465 Merge pull request #51 from jbottigliero/feature-instanceof-Promise
  • 839e367 feat: "instanceof": "Promise"
  • ea618a2 docs: update badge
  • 2ba1418 3.0.0
  • 52f8024 Merge pull request #43 from epoberezkin/greenkeeper/json-schema-test-2.0.0
  • 2ee86a0 Merge pull request #48 from epoberezkin/beta
  • 1b6a239 Merge branch 'master' into beta
  • 5b0c5a4 fix: update for ajv v6.0.0
  • 733e33b chore(package): update json-schema-test to version 2.0.0
  • 506b850 3.0.0-beta.0
  • 762069e refactor: remove keyword if/then/else (to ajv), closes #41, epoberezkin/ajv#586

See the full diff

FAQ and help

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


Your Greenkeeper bot 馃尨

@googlebot
Copy link

So there's good news and bad news.

馃憤 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

馃槙 The bad news is that it appears that one or more commits were authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this State. It's up to you to confirm consent of the commit author(s) and merge this pull request when appropriate.

@rsimha
Copy link
Contributor

rsimha commented Jan 31, 2018

/to @cramforce @erwinmombay

@googlebot
Copy link

A Googler has manually verified that the CLAs look good, thanks! They commented:

> all commits are from greenkeeper

@rsimha rsimha merged commit c32aa63 into master Jan 31, 2018
@rsimha rsimha deleted the greenkeeper/ajv-keywords-3.1.0 branch January 31, 2018 22:34
RanAbram pushed a commit to RanAbram/amphtml that referenced this pull request Mar 12, 2018
protonate pushed a commit to protonate/amphtml that referenced this pull request Mar 15, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants