Skip to content

Conversation

@greenkeeperio-bot
Copy link

Hello lovely humans,

gulp-exclude-gitignore just published its new version 1.1.1.

State Failing tests 🚨
Dependency gulp-exclude-gitignore
New version 1.1.1
Type devDependency

This version is covered by your current version range and after updating it in your project the build went from success to failure.

As gulp-exclude-gitignore is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.

Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?

There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.

Good luck with your project ✨

You rock!

🌴


GitHub Release

  • Support for Node 0.12

The new version differs by 11 commits .

  • ba0af6e 1.1.1
  • 044e46c Don't run tests on node 0.12 to keep up with the environment
  • 5f46bcd Fix for Node 0.12 - Fix #5
  • 2a3e4fd 1.1.0
  • dd88341 Update tooling to generator-node defaults
  • d0214ee Properly account for nested .gitignore - Fix #2
  • 359a7c0 Update to work with gulp-match 2
  • d98f790 chore(package): update dependencies (#4)
  • ebf9e10 Update .travis.yml
  • 2c13bbe Merge pull request #1 from jmeshen/patch-2
  • 07e6b24 Update README.md

See the full diff.


This pull request was created by greenkeeper.io.

Tired of seeing this sponsor message? ⚡ greenkeeper upgrade

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.

3 participants