utils/node-apt
1
0
Fork 0
Code Issues Pull Requests 1 Actions Releases 6 Wiki Activity

Bump express-rate-limit from 6.11.2 to 7.0.2 #34

Merged
dependabot[bot] merged 1 commits from dependabot/npm_and_yarn/express-rate-limit-7.0.2 into main 2023-10-01 21:37:31 +00:00
Conversation 0 Commits 1 Files Changed 1 +1 -1
dependabot[bot] commented 2023-10-01 20:39:55 +00:00 (Migrated from github.com)
Copy Link

Bumps express-rate-limit from 6.11.2 to 7.0.2.

Release notes

Sourced from express-rate-limit's releases.

v7.0.2

You can view the changelog here.

v7.0.1

You can view the 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.
Changelog

Sourced from express-rate-limit's changelog.

7.0.2

Added

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

7.0.1

Added

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

7.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

... (truncated)

Commits
  • c1fd7b8 7.0.2
  • 5d4658f v7.0.2 changelog
  • 9d8f136 formatting
  • 62559e9 Update readme.md
  • 3713d59 add cluster-memory-store & call it out in usage section
  • c58ecbb docs: mention that external store support was added in v2.3.0
  • c147da5 Remove a misstatement I added about Legacy stores not supporting resetTime - ...
  • 5d291dd chore: remove unused dep
  • c395374 docs: memcached is now a modern store🎉 (#402)
  • e641a54 7.0.1
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Bumps [express-rate-limit](https://github.com/express-rate-limit/express-rate-limit) from 6.11.2 to 7.0.2. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/express-rate-limit/express-rate-limit/releases">express-rate-limit's releases</a>.</em></p> <blockquote> <h2>v7.0.2</h2> <p>You can view the changelog <a href="https://github.com/express-rate-limit/express-rate-limit/blob/main/changelog.md">here</a>.</p> <h2>v7.0.1</h2> <p>You can view the changelog <a href="https://github.com/express-rate-limit/express-rate-limit/blob/main/changelog.md">here</a>.</p> <h2>v7.0.0</h2> <h3>Breaking</h3> <ul> <li>Changed behavior when <code>max</code> is set to 0: <ul> <li>Previously, <code>max: 0</code> was treated as a 'disable' flag and would allow all requests through.</li> <li>Starting with v7, all requests will be blocked when max is set to 0.</li> <li>To replicate the old behavior, use the <a href="https://github.com/express-rate-limit/express-rate-limit#skip">skip</a> function instead.</li> </ul> </li> <li>Renamed <code>req.rateLimit.current</code> to <code>req.rateLimit.used</code>. <ul> <li><code>current</code> is now a hidden getter that will return the <code>used</code> value, but it will not appear when iterating over the keys or calling <code>JSON.stringify()</code>.</li> </ul> </li> <li>Changed the minimum required Node version from v14 to v16. <ul> <li><code>express-rate-limit</code> now targets <code>es2022</code> in TypeScript/ESBuild.</li> </ul> </li> <li>Bumped TypeScript from v4 to v5 and <code>dts-bundle-generator</code> from v7 to v8.</li> </ul> <h3>Deprecated</h3> <ul> <li>Removed the <code>draft_polli_ratelimit_headers</code> option (it was deprecated in v6). <ul> <li>Use <code>standardHeaders: 'draft-6'</code> instead.</li> </ul> </li> <li>Removed the <code>onLimitReached</code> option (it was deprecated in v6). <ul> <li><a href="(https://github.com/express-rate-limit/express-rate-limit/wiki/Error-Codes#wrn_erl_deprecated_on_limit_reached)">This</a> is an example of how to replicate it's behavior with a custom <code>handler</code> option.</li> </ul> </li> </ul> <h3>Changed</h3> <ul> <li>The <code>MemoryStore</code> now uses precise, per-user reset times rather than a global window that resets all users at once.</li> <li>The <code>limit</code> configuration option is now prefered to <code>max</code>. <ul> <li>It still shows the same behavior, and <code>max</code> is still supported. The change was made to better align with terminology used in the IETF standard drafts.</li> </ul> </li> </ul> <h3>Added</h3> <ul> <li>The <code>validate</code> config option can now be an object with keys to enable or disable specific validation checks. For more information, see <a href="https://github.com/express-rate-limit/express-rate-limit#validate">this</a>.</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/express-rate-limit/express-rate-limit/blob/main/changelog.md">express-rate-limit's changelog</a>.</em></p> <blockquote> <h2><a href="https://github.com/express-rate-limit/express-rate-limit/releases/tag/v7.0.2">7.0.2</a></h2> <h3>Added</h3> <ul> <li>Added <code>cluster-memory-store</code> to the readme and made a couple of other minor clarifications.</li> </ul> <h2><a href="https://github.com/express-rate-limit/express-rate-limit/releases/tag/v7.0.1">7.0.1</a></h2> <h3>Added</h3> <ul> <li>Added <code>rate-limit-postgresql</code> to the <code>stores</code> list in the readme.</li> </ul> <h2><a href="https://github.com/express-rate-limit/express-rate-limit/releases/tag/v7.0.0">7.0.0</a></h2> <h3>Breaking</h3> <ul> <li>Changed behavior when <code>max</code> is set to 0: <ul> <li>Previously, <code>max: 0</code> was treated as a 'disable' flag and would allow all requests through.</li> <li>Starting with v7, all requests will be blocked when max is set to 0.</li> <li>To replicate the old behavior, use the <a href="https://github.com/express-rate-limit/express-rate-limit#skip">skip</a> function instead.</li> </ul> </li> <li>Renamed <code>req.rateLimit.current</code> to <code>req.rateLimit.used</code>. <ul> <li><code>current</code> is now a hidden getter that will return the <code>used</code> value, but it will not appear when iterating over the keys or calling <code>JSON.stringify()</code>.</li> </ul> </li> <li>Changed the minimum required Node version from v14 to v16. <ul> <li><code>express-rate-limit</code> now targets <code>es2022</code> in TypeScript/ESBuild.</li> </ul> </li> <li>Bumped TypeScript from v4 to v5 and <code>dts-bundle-generator</code> from v7 to v8.</li> </ul> <h3>Deprecated</h3> <ul> <li>Removed the <code>draft_polli_ratelimit_headers</code> option (it was deprecated in v6). <ul> <li>Use <code>standardHeaders: 'draft-6'</code> instead.</li> </ul> </li> <li>Removed the <code>onLimitReached</code> option (it was deprecated in v6). <ul> <li><a href="(https://github.com/express-rate-limit/express-rate-limit/wiki/Error-Codes#wrn_erl_deprecated_on_limit_reached)">This</a> is an example of how to replicate it's behavior with a custom <code>handler</code> option.</li> </ul> </li> </ul> <h3>Changed</h3> <ul> <li>The <code>MemoryStore</code> now uses precise, per-user reset times rather than a global window that resets all users at once.</li> <li>The <code>limit</code> configuration option is now prefered to <code>max</code>. <ul> <li>It still shows the same behavior, and <code>max</code> is still supported. The change was made to better align with terminology used in the IETF standard drafts.</li> </ul> </li> </ul> <h3>Added</h3> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/express-rate-limit/express-rate-limit/commit/c1fd7b82bc2ef9995bae160d52003eaeadff9616"><code>c1fd7b8</code></a> 7.0.2</li> <li><a href="https://github.com/express-rate-limit/express-rate-limit/commit/5d4658fabe2ec5ef71e18976126832d763641a58"><code>5d4658f</code></a> v7.0.2 changelog</li> <li><a href="https://github.com/express-rate-limit/express-rate-limit/commit/9d8f13634c15fcc2a0829b49e8a9551e4875458c"><code>9d8f136</code></a> formatting</li> <li><a href="https://github.com/express-rate-limit/express-rate-limit/commit/62559e912ac94f2d676f45897bc03d8495859d5e"><code>62559e9</code></a> Update readme.md</li> <li><a href="https://github.com/express-rate-limit/express-rate-limit/commit/3713d5994615acdfea68942ee8360ab806305279"><code>3713d59</code></a> add cluster-memory-store &amp; call it out in usage section</li> <li><a href="https://github.com/express-rate-limit/express-rate-limit/commit/c58ecbb14cc9d121cfc142e96095ee4cfcf97955"><code>c58ecbb</code></a> docs: mention that external store support was added in v2.3.0</li> <li><a href="https://github.com/express-rate-limit/express-rate-limit/commit/c147da535c95bda17d4f44d4e7a548e52edccc4c"><code>c147da5</code></a> Remove a misstatement I added about Legacy stores not supporting resetTime - ...</li> <li><a href="https://github.com/express-rate-limit/express-rate-limit/commit/5d291dd84d35e5e3be96c74679626bb88227cf51"><code>5d291dd</code></a> chore: remove unused dep</li> <li><a href="https://github.com/express-rate-limit/express-rate-limit/commit/c39537416ed12abf6a5aef2ab1625d3e640d809b"><code>c395374</code></a> docs: memcached is now a modern store🎉 (<a href="https://redirect.github.com/express-rate-limit/express-rate-limit/issues/402">#402</a>)</li> <li><a href="https://github.com/express-rate-limit/express-rate-limit/commit/e641a54ee86a49260152d71813e481abda990e1c"><code>e641a54</code></a> 7.0.1</li> <li>Additional commits viewable in <a href="https://github.com/express-rate-limit/express-rate-limit/compare/v6.11.2...v7.0.2">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=express-rate-limit&package-manager=npm_and_yarn&previous-version=6.11.2&new-version=7.0.2)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details>
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
bug
Something isn't working
dependencies
Pull requests that update a dependency file
documentation
Improvements or additions to documentation
duplicate
This issue or pull request already exists
enhancement
New feature or request
github_actions
Pull requests that update GitHub Actions code
good first issue
Good for newcomers
help wanted
Extra attention is needed
invalid
This doesn't seem right
javascript
Pull requests that update Javascript code
question
Further information is requested
wontfix
This will not be worked on
bug
Something is not working
duplicate
This issue or pull request already exists
enhancement
New feature
help wanted
Need some help
invalid
Something is wrong
question
More information is needed
wontfix
This won't be fixed
No Label
dependencies
javascript
Milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: utils/node-apt#34
No description provided.
Delete Branch "dependabot/npm_and_yarn/express-rate-limit-7.0.2"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?