fix(deps): update dependency express-rate-limit to v7

[renovate[bot]]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
express-rate-limit	^6.2.0 -> ^7.0.0

---

Release Notes

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

v7.3.1

Compare Source

You can view the changelog here.

v7.3.0

Compare Source

You can view the changelog here.

v7.2.0

Compare Source

You can view the changelog here.

v7.1.5

Compare Source

You can view the changelog here.

v7.1.4

Compare Source

You can view the changelog here.

v7.1.3

Compare Source

You can view the changelog here.

v7.1.2

Compare Source

Changed

• Re-organized documentation from readme into docs/ folder and added documentation website.

v7.1.1

Compare Source

Misc

• Enabled provenance statement generation, see https://github.com/express-rate-limit/express-rate-limit#406.

---

You can view the full changelog here.

v7.1.0

Compare Source

Changed

• The getKey method is now always defined. If the store does not have the required get method, getKey will throw an error explaining this.

v7.0.2

Compare Source

You can view the changelog here.

v7.0.1

Compare Source

You can view the changelog here.

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 - At any time (no schedule defined), 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.