fix(deps): update dependency express-rate-limit to v8 #1365

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.

Sign up for GitHub

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

Jump to bottom

Open

renovate wants to merge 1 commit into v5 from renovate/express-rate-limit-8.x

Contributor

renovate bot commented Jul 15, 2025 •

edited

Loading

This PR contains the following updates:

Package	Change	Age	Confidence
express-rate-limit	`^6.2.0` -> `^8.0.0`

Release Notes

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

`v8.2.1`

You can view the changelog here.

`v8.2.0`

You can view the changelog here.

`v8.1.0`

You can view the changelog here.

`v8.0.1`

You can view the changelog here.

`v8.0.0`

You can view the changelog here.

`v7.5.1`

Changed

Narrowed type of standardHeaders from string to just the supported values via a TypeScript const assertion (#506)

You can view the full changelog here.

`v7.5.0`

Added

Implemented the combined RateLimit header according to the eighth draft of the IETF RateLimit header specificiation. Enable by setting standardHeaders: 'draft-8'.
Added a new identifier option, used as the name for the quota policy in the draft-8 headers.
Added a new headersDraftVersion validation check to identifies cases where an unsupported version string is passed to the standardHeaders option.

You can view the full changelog here.

`v7.4.1`

Fixed

Made the passOnStoreError return after calling next() rather than continuing execution.

You can view the full changelog here.

`v7.4.0`

Added

Added passOnStoreError option to allow a way to "fail open" in the event of a backend error.

You can view the full changelog here.

`v7.3.1`

Fixed

Changed error displayed for the creationStack validation check when a store
with localKeys set to false is used.
Improved documentation for the creationStack check.

You can view the full changelog here.

`v7.3.0`

Added

Added a new unsharedStore validation check that identifies cases where a
single store instance is shared across multiple limiters.

You can view the full changelog here.

`v7.2.0`

Added

Added a new creationStack validation check that looks for instances created
in a request handler.

You can view the full changelog here.

`v7.1.5`

Fixed

Enable async requestWasSuccessful methods to work as documented.

You can view the full changelog here.

`v7.1.4`

Fixed

Ensure header values are strings rather than numbers, for compatibility with
Bun.

You can view the full changelog here.

`v7.1.3`

Changed

Loosened peer dependencies to explicitly allow the Express 5 beta. (See
#415)

You can view the full changelog here.

`v7.1.2`

Changed

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

You can view the full changelog here.

`v7.1.1`

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`

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.

You can view the full changelog here.

`v7.0.2`

Added

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

You can view the full changelog here.

`v7.0.1`

Added

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

You can view the full changelog here.

`v7.0.0`

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 was generated by Mend Renovate. View the repository job log.


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

dda5333

renovate bot requested review from DarrenOfficial and SudhanPlayz as code owners

July 15, 2025 19:27

Contributor

coderabbitai bot commented Jul 15, 2025

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

Review comments: Directly reply to a review comment made by CodeRabbit. Example:
- I pushed a fix in commit <commit_id>, please review it.
- Explain this complex logic.
- Open a follow-up GitHub issue for this discussion.
Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
- @coderabbitai explain this code block.
- @coderabbitai modularize this function.
PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
- @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
- @coderabbitai read src/utils.ts and explain its main purpose.
- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
- @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Join our Discord community for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

@coderabbitai pause to pause the reviews on a PR.
@coderabbitai resume to resume the paused reviews.
@coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
@coderabbitai full review to do a full review from scratch and review all the files again.
@coderabbitai summary to regenerate the summary of the PR.
@coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
@coderabbitai resolve resolve all the CodeRabbit review comments.
@coderabbitai configuration to show the current CodeRabbit configuration for the repository.
@coderabbitai help to get help.

Other keywords and placeholders

Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (`.coderabbit.yaml`)

You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
Please see the configuration documentation for more information.
If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

Visit our Documentation for detailed information on how to use CodeRabbit.
Join our Discord Community to get help, request features, and share feedback.
Follow us on X/Twitter for updates and announcements.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet