Skip to content
This repository has been archived by the owner on Oct 23, 2023. It is now read-only.

Update js-yaml to the latest version 🚀 #266

Merged
merged 1 commit into from
Mar 8, 2018

Conversation

greenkeeper[bot]
Copy link

@greenkeeper greenkeeper bot commented Mar 5, 2018

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 3.11.0 of js-yaml was just published.

Dependency js-yaml
Current Version 3.10.0
Type dependency

The version 3.11.0 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.

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

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’t 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 5 commits.

  • f2bb207 3.11.0 released
  • b7eb2e6 Browser files rebuild
  • dc2227b Dumper: fix negative integers in bin/octal/hex formats, close #399
  • c62fd62 support es6 arrow functions, fixes #389 (#393)
  • bee7e99 Fix typo in README.md (#373)

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 greenkeeper bot added the renovate label Mar 5, 2018
@faselbaum faselbaum merged commit 122e071 into master Mar 8, 2018
@greenkeeper greenkeeper bot deleted the greenkeeper/js-yaml-3.11.0 branch March 8, 2018 11:06
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant