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

## The dependency [express-session](https://github.com/expressjs/session) was updated from `1.16.1` to `1.16.2`.

🚨 [View failing branch](https://github.com/aethant/merino/compare/master...aethant:greenkeeper%2Fexpress-session-1.16.2).

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/travis-ci/push:** The Travis CI build failed ([Details](https://travis-ci.org/aethant/merino/builds/544562095?utm_source=github_status&utm_medium=notification)).

---

Release Notes for 1.16.2

• Fix restoring cookie.originalMaxAge when store returns Date


• deps: parseurl@~1.3.3

Commits

The new version differs by 18 commits.

• 2d54f0d 1.16.2


• 30e23f1 Fix restoring cookie.originalMaxAge when store returns Date


• 479940a tests: add cookie.originalMaxAge tests


• 97fe63c docs: add @google-cloud/connect-firestore to the list of session stores


• bff097e docs: add connect-typeorm to the list of session stores


• fb498ac build: Node.js@12.4


• 1c75fa0 build: Node.js@11.15


• ad90250 build: Node.js@10.16


• 969e4c1 build: express@4.17.1


• 8d6430e build: nyc@14.1.1


• e0feb04 build: support Node.js 12.x


• 327695e build: Node.js@11.14


• 268c929 build: Node.js@8.16


• 3d5fa06 build: use nyc for coverage testing


• 1588ef6 docs: add connect-hazelcast to the list of session stores

There are 18 commits in total.

See the full diff

FAQ and help

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

---

Your [Greenkeeper](https://greenkeeper.io) Bot :palm_tree: