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 metalsmith-ignore to the latest version 馃殌 #143

Closed
wants to merge 2 commits into from

Conversation

greenkeeper[bot]
Copy link
Contributor

@greenkeeper greenkeeper bot commented Sep 12, 2018

Version 1.0.0 of metalsmith-ignore was just published.

Dependency metalsmith-ignore
Current Version 0.1.2
Type devDependency

The version 1.0.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 metalsmith-ignore.

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.


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 馃尨

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling fecc0eb on greenkeeper/metalsmith-ignore-1.0.0 into b685b98 on master.

@scurker scurker closed this Sep 18, 2018
@greenkeeper greenkeeper bot deleted the greenkeeper/metalsmith-ignore-1.0.0 branch September 18, 2018 03:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants