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 firefox-profile to the latest version 🚀 #1359

Merged
merged 1 commit into from
Aug 23, 2018

Conversation

greenkeeper[bot]
Copy link
Contributor

@greenkeeper greenkeeper bot commented Aug 20, 2018

Version 1.2.0 of firefox-profile was just published.

Dependency firefox-profile
Current Version 1.1.0
Type dependency

The version 1.2.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 firefox-profile.

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 4 commits.

  • a0a3b76 version bump
  • 96c1004 Merge pull request #99 from saadtazi/security-audit-fix
  • a79ea8f drop support for node 4
  • 3c50dce deps version bump

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

Coverage Status

Coverage remained the same at 100.0% when pulling becebdf on greenkeeper/firefox-profile-1.2.0 into 8f03dfd on master.

@rpl
Copy link
Member

rpl commented Aug 23, 2018

There is an intermittent failure from one of the appveyor jobs (https://ci.appveyor.com/project/kumar303/web-ext/build/1.0.1795/job/u9poru0h1kmgjhy4#L2324), but it seems to be totally unrelated to this change (and as an additional confirmation the same failure has been also triggered in one of the other PR, #1357, and the change applied in that PR can't be what triggered the intermittent failure).

I'm taking a look at those appveyor failure, but I'm going to merge this PR in the meantime.

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