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

chore(deps): update dependency express-rate-limit to v7 #413

Merged
merged 1 commit into from
Oct 1, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 17, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
express-rate-limit ^6.11.2 -> ^7.0.2 age adoption passing confidence

Release Notes

express-rate-limit/express-rate-limit (express-rate-limit)

v7.0.2

Compare Source

Added
  • Added cluster-memory-store to the readme and made a couple of other minor
    clarifications.

v7.0.1

Compare Source

Added
  • Added rate-limit-postgresql to the stores list in the readme.

v7.0.0

Compare Source

Breaking
  • Changed behavior when max is set to 0:
    • Previously, max: 0 was treated as a 'disable' flag and would allow all
      requests through.
    • Starting with v7, all requests will be blocked when max is set to 0.
    • To replicate the old behavior, use the
      skip
      function instead.
  • Renamed req.rateLimit.current to req.rateLimit.used.
    • current is now a hidden getter that will return the used value, but it
      will not appear when iterating over the keys or calling JSON.stringify().
  • Changed the minimum required Node version from v14 to v16.
    • express-rate-limit now targets es2022 in TypeScript/ESBuild.
  • Bumped TypeScript from v4 to v5 and dts-bundle-generator from v7 to v8.
Deprecated
  • Removed the draft_polli_ratelimit_headers option (it was deprecated in v6).
    • Use standardHeaders: 'draft-6' instead.
  • Removed the onLimitReached option (it was deprecated in v6).
    • This
      is an example of how to replicate it's behavior with a custom handler
      option.
Changed
  • The MemoryStore now uses precise, per-user reset times rather than a global
    window that resets all users at once.
  • The limit configuration option is now prefered to max.
    • It still shows the same behavior, and max is still supported. The change
      was made to better align with terminology used in the IETF standard drafts.
Added
  • The validate config option can now be an object with keys to enable or
    disable specific validation checks. For more information, see
    this.

Configuration

📅 Schedule: Branch creation - "before 12pm on Sunday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@ijsblokjeee ijsblokjeee bot added Dependencies 🚀 PRs and Issues related to dependencies Chore 🧹 labels Sep 17, 2023
@renovate renovate bot force-pushed the renovate/express-rate-limit-7.x branch from 6799d76 to 0b67679 Compare September 17, 2023 01:05
@renovate renovate bot force-pushed the renovate/express-rate-limit-7.x branch from 0b67679 to 034fe50 Compare September 26, 2023 22:01
@ijsKoud ijsKoud merged commit 4e76f4d into main Oct 1, 2023
6 checks passed
@ijsKoud ijsKoud deleted the renovate/express-rate-limit-7.x branch October 1, 2023 14:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Chore 🧹 Dependencies 🚀 PRs and Issues related to dependencies
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant