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 express-session is breaking the build 🚨 #181

Open
greenkeeper bot opened this issue Oct 11, 2019 · 2 comments
Open

An in-range update of express-session is breaking the build 🚨 #181

greenkeeper bot opened this issue Oct 11, 2019 · 2 comments

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Oct 11, 2019

The dependency express-session was updated from 1.16.2 to 1.17.0.

🚨 View failing branch.

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

express-session is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/appveyor/branch: Waiting for AppVeyor build to complete (Details).
  • continuous-integration/travis-ci/push: The Travis CI build is in progress (Details).
  • SockRPG: Build failed (Details).

Release Notes for 1.17.0
  • deps: cookie@0.4.0
    • Add SameSite=None support
  • deps: safe-buffer@5.2.0
Commits

The new version differs by 12 commits.

  • b22384b 1.17.0
  • 4d25340 build: fix coverage reporting
  • c32ad19 docs: expand description of the rolling option
  • 9a5e313 docs: add lowdb-session-store to the list of session stores
  • 9c06509 build: mocha@6.2.1
  • 8731d7b build: Node.js@12.11
  • 10607bd deps: safe-buffer@5.2.0
  • 1684c54 deps: cookie@0.4.0
  • 8de7865 docs: add express-session-rsdb to the list of session stores
  • f75ed7e build: fix readme lint out of order message
  • 2719bef build: Node.js@12.8
  • 6db8e04 build: mocha@6.2.0

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 Oct 11, 2019

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

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Apr 17, 2020

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 25 commits.

There are 25 commits in total.

See the full diff

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