[Snyk] Upgrade express-session from 1.17.0 to 1.17.2

[snyk-bot]

Snyk has created this PR to upgrade express-session from 1.17.0 to 1.17.2.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 2 versions ahead of your current version.
• The recommended version was released 2 months ago, on 2021-05-19.

Release notes

Package name: express-session

• 1.17.2 - 2021-05-19
  
  • Fix res.end patch to always commit headers
  • deps: cookie@0.4.1
  • deps: safe-buffer@5.2.1
• 1.17.1 - 2020-04-17
  
  • Fix internal method wrapping error on failed reloads
• 1.17.0 - 2019-10-11
  
  • deps: cookie@0.4.0
    • Add SameSite=None support
  • deps: safe-buffer@5.2.0

from express-session GitHub release notes

Commit messages

Package name: express-session

• 0048bca 1.17.2
• 4baea4a build: Node.js@16.2
• 45cbbf4 bulid: eslint-plugin-markdown@2.1.0
• 9a1cc15 build: eslint@7.26.0
• 7ff50af build: use GitHub Actions instead of Travis CI
• b23ec4f docs: note about samesite attribute and secure requirements
• 034fd4e build: supertest@6.1.3
• a811b59 docs: add @ databunker/session-store to the list of session stores
• 5cf60e2 docs: add better-sqlite3-session-store to the list of session stores
• 579154a build: Node.js@12.22
• 657e3c0 build: mocha@8.4.0
• f44f0e4 build: support Node.js 16.x
• e007c85 build: Node.js@15.12
• 373514d build: mocha@8.3.1
• 6e4052d build: Node.js@15.10
• c1df7c5 build: Node.js@14.16
• 3acbb81 build: Node.js@10.24
• 7a6c479 build: Node.js@12.21
• acca908 build: Node.js@15.6
• 54e4193 build: supertest@6.1.1
• a26b4d3 build: Node.js@10.23
• 1813cd4 build: Node.js@14.15
• 7452225 build: Node.js@15.4
• 8914d60 build: Node.js@12.20

Compare

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[pull-request-quantifier-deprecated]

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Small
Size       : +1 -1
Percentile : 0.8%

Total files changed: 1

Change summary by file extension:
.json : +1 -1

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detetcted.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.