Skip to content

Conversation

greenkeeper[bot]
Copy link
Contributor

@greenkeeper greenkeeper bot commented Jun 23, 2019

The dependency node-yaml was updated from 3.2.0 to 4.0.0.

This version is not covered by your current version range.

If you don’t 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.


Release Notes for 4.0.0

Add:

  • Native ESM support
  • Tests that cover almost all codebase

Update:

  • Project has been rewritten on JavaScript
  • Improved documentation

Remove:

  • js-yaml has been moved to peerDependencies, so you need to install it manually
  • Remove schemas and another reused exports (such as parser, createSchema and so on) of js-yaml, which means that you need to use these things from js-yaml.
  • write() and read() functions will always return a Promise. Callback API is not available anymore.

For this release I've decided to rewrite the project from scratch. So, this release is not backward compatible

All changes: 4e1f234...ebffd85

Commits

The new version differs by 38 commits.

There are 38 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 🌴

@coveralls
Copy link

Pull Request Test Coverage Report for Build 43

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 90.0%

Totals Coverage Status
Change from base Build 41: 0.0%
Covered Lines: 52
Relevant Lines: 53

💛 - Coveralls

@huang-xiao-jian huang-xiao-jian merged commit 0fe1193 into master Jun 24, 2019
@greenkeeper greenkeeper bot deleted the greenkeeper/node-yaml-4.0.0 branch June 24, 2019 08:22
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.

2 participants