Skip to content

Conversation

@greenkeeperio-bot
Copy link
Contributor

Hello lovely humans,

config just published its new version 1.23.0.

State Failing tests 🚨
Dependency config
New version 1.23.0
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 config 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!

🌴


The new version differs by 11 commits .

  • 5aed595 Re-publishing because npmjs didn't see 1.22
  • 6c0bb5f History and package updates
  • c676464 Merge pull request #351 from simon-scherzinger/master
  • 9c9aeee Merge pull request #340 from patrickpilch/raw-config-wrapper
  • 8886462 adds second parameter to defer function stub
  • d6196fd test original values in deferredConfig
  • 662042d save original value in deferredConfig
  • 6f504d6 Merge pull request #350 from wmertens/loadFileConfigs
  • 12eb36b util.loadFileConfigs: support optional source dir
  • c567f62 Initial tests for util.initParam, passing.
  • e71f552 Issue #338 Adding raw wrapper to prevent object modification in configuration

See the full diff.


This pull request was created by greenkeeper.io.

Tired of seeing this sponsor message? ⚡ greenkeeper upgrade

@coveralls
Copy link

coveralls commented Nov 2, 2016

Coverage Status

Coverage remained the same at 100.0% when pulling 3a3f373 on greenkeeper-config-1.23.0 into 8587507 on master.

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.

4 participants