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 is breaking the build 🚨 #43

Open
greenkeeper bot opened this issue Sep 26, 2019 · 1 comment
Open

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

greenkeeper bot opened this issue Sep 26, 2019 · 1 comment

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Sep 26, 2019

The devDependency serve was updated from 11.1.0 to 11.2.0.

🚨 View failing branch.

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

serve is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for 11.2.0

Minor Changes

  • Add support for manual SSL certs/keys: #520

Patches

  • Fixed ZEIT Now reference in readme: #554
  • Add information about how to serve a specific path: #548
  • Bumped serve-handler to the latest version: #559

Credits

Huge thanks to @mattdodge, @d2s, and @Johann-S for helping!

Commits

The new version differs by 5 commits.

  • cbc6c4a 11.2.0
  • 9360686 Bumped serve-handler to the latest version (#559)
  • aa00e2c Add information about how to serve a specific path (#548)
  • 550a76e Fixed ZEIT Now reference in readme (#554)
  • 70d957b Add support for manual SSL certs/keys (#520)

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 🌴

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Sep 26, 2019

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

0 participants