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

An in-range update of serve-static is breaking the build 🚨 #1199

Closed
greenkeeper bot opened this issue Sep 29, 2017 · 1 comment
Closed

An in-range update of serve-static is breaking the build 🚨 #1199

greenkeeper bot opened this issue Sep 29, 2017 · 1 comment

Comments

@greenkeeper
Copy link
Contributor

@greenkeeper greenkeeper bot commented Sep 29, 2017

Version 1.13.1 of serve-static just got published.

Branch Build failing 🚨
Dependency serve-static
Current Version 1.13.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As serve-static 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 💪

Status Details
  • continuous-integration/appveyor/branch AppVeyor build succeeded Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes 1.13.1
  • Fix regression when root is incorrectly set to a file
  • deps: send@0.16.1
Commits

The new version differs by 3 commits.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

@greenkeeper greenkeeper bot added the greenkeeper label Sep 29, 2017
@greenkeeper

This comment has been minimized.

Copy link
Contributor Author

@greenkeeper greenkeeper bot commented Sep 29, 2017

After pinning to 1.13.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

@lock lock bot locked as resolved and limited conversation to collaborators May 9, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.