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

refactor: Upgrade express-rate-limit from 6.11.2 to 7.2.0 #9048

Open
wants to merge 1 commit into
base: alpha
Choose a base branch
from

Conversation

parseplatformorg
Copy link
Contributor

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.

  • The recommended version is 10 versions ahead of your current version.
  • The recommended version was released 22 days ago, on 2024-03-02.
Release notes
Package name: express-rate-limit
  • 7.2.0 - 2024-03-02

    You can view the changelog here.

  • 7.1.5 - 2023-11-27

    You can view the changelog here.

  • 7.1.4 - 2023-11-06

    You can view the changelog here.

  • 7.1.3 - 2023-10-26

    You can view the changelog here.

  • 7.1.2 - 2023-10-23

    You can view the changelog here.

  • 7.1.1 - 2023-10-09

    Misc


    You can view the full changelog here.

  • 7.1.0 - 2023-10-04

    You can view the changelog here.

  • 7.0.2 - 2023-09-26

    You can view the changelog here.

  • 7.0.1 - 2023-09-16

    You can view the changelog here.

  • 7.0.0 - 2023-09-12

    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.
  • 6.11.2 - 2023-09-12
from express-rate-limit GitHub release notes
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

Copy link

I will reformat the title to use the proper commit message syntax.

@parse-github-assistant parse-github-assistant bot changed the title [Snyk] Upgrade express-rate-limit from 6.11.2 to 7.2.0 refactor: Upgrade express-rate-limit from 6.11.2 to 7.2.0 Mar 24, 2024
Copy link

Thanks for opening this pull request!

  • ❌ Please link an issue that describes the reason for this pull request, otherwise your pull request will be closed. Make sure to write it as Closes: #123 in the PR description, so I can recognize it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants