refactor: Upgrade express-rate-limit from 6.11.2 to 7.2.0 #9048
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR was automatically created by Snyk using the credentials of a real user.
Snyk has created this PR to upgrade express-rate-limit from 6.11.2 to 7.2.0.
ℹ️ 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.
Warning: This is a major version upgrade, and may be a breaking change.
Release notes
Package name: express-rate-limit
-
7.2.0 - 2024-03-02
-
7.1.5 - 2023-11-27
-
7.1.4 - 2023-11-06
-
7.1.3 - 2023-10-26
-
7.1.2 - 2023-10-23
-
7.1.1 - 2023-10-09
- Enabled provenance statement generation, see https://github.com/express-rate-limit/express-rate-limit#406.
-
7.1.0 - 2023-10-04
-
7.0.2 - 2023-09-26
-
7.0.1 - 2023-09-16
-
7.0.0 - 2023-09-12
- Changed behavior when
- Previously,
- 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
- Changed the minimum required Node version from v14 to v16.
- Bumped TypeScript from v4 to v5 and
- Removed the
- Use
- Removed the
- This is an example of how to replicate it's behavior with a custom
- The
- The
- It still shows the same behavior, and
- The
-
6.11.2 - 2023-09-12
from express-rate-limit GitHub release notesYou can view the changelog here.
You can view the changelog here.
You can view the changelog here.
You can view the changelog here.
You can view the changelog here.
Misc
You can view the full changelog here.
You can view the changelog here.
You can view the changelog here.
You can view the changelog here.
Breaking
maxis set to 0:max: 0was treated as a 'disable' flag and would allow all requests through.req.rateLimit.currenttoreq.rateLimit.used.currentis now a hidden getter that will return theusedvalue, but it will not appear when iterating over the keys or callingJSON.stringify().express-rate-limitnow targetses2022in TypeScript/ESBuild.dts-bundle-generatorfrom v7 to v8.Deprecated
draft_polli_ratelimit_headersoption (it was deprecated in v6).standardHeaders: 'draft-6'instead.onLimitReachedoption (it was deprecated in v6).handleroption.Changed
MemoryStorenow uses precise, per-user reset times rather than a global window that resets all users at once.limitconfiguration option is now prefered tomax.maxis still supported. The change was made to better align with terminology used in the IETF standard drafts.Added
validateconfig option can now be an object with keys to enable or disable specific validation checks. For more information, see this.Commit messages
Package name: express-rate-limit
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