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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update update-notifier to the latest version 🚀 #45

Merged
merged 2 commits into from
Jun 12, 2019

Conversation

greenkeeper[bot]
Copy link
Contributor

@greenkeeper greenkeeper bot commented May 10, 2019

The dependency update-notifier was updated from 2.5.0 to 3.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 v3.0.0
  • Add supports for yarn
  • Drop support for Node 6
Commits

The new version differs by 10 commits.

  • a7bb3ee 3.0.0
  • ad8ed1b Suggest yarn when installed with yarn (#132)
  • 5f06620 Exit the update check process if it does not respond after 30s (#156)
  • 79e89ad Fix failing test (#155)
  • c8faa84 Add distTag option (#151)
  • 14632e4 Add failing test for #153 (#154)
  • aafd8a0 Require Node.js 8
  • 0d49f51 Add Tidelift mention in the readme
  • 8df01b3 Fix docs position of shouldNotifyInNpmScript (#143)
  • d371834 Docs: isGlobal option does not default to true (#142)

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 🌴

@nitriques nitriques changed the base branch from master to dev June 12, 2019 15:03
@nitriques nitriques merged commit 2c359a6 into dev Jun 12, 2019
@nitriques nitriques deleted the greenkeeper/update-notifier-3.0.0 branch June 12, 2019 15:04
@wilhelmer
Copy link

wilhelmer commented Jun 19, 2019

@nitriques Note that update-notifier 3.0.0 requires Node.js 8. The old version 2.5.0 only required Node.js 4.

This means that algolia-webcrawler 3.2.1 now effectively requires Node 8. I'm running v6.16.0 on my server and algolia-webcrawler crashed on startup ("unexpected token").

Had to downgrade update-notifier to 2.5.0 to make algolia-webcrawler 3.2.1 work.

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