fix(deps): update dependency express-rate-limit to v7 #286
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 contains the following updates:
6.7.0
->7.5.1
Release Notes
express-rate-limit/express-rate-limit (express-rate-limit)
v7.5.1
Compare Source
You can view the changelog here.
v7.5.0
Compare Source
Added
RateLimit
header according to the eighth draft of the IETF RateLimit header specificiation. Enable by settingstandardHeaders: 'draft-8'
.identifier
option, used as the name for the quota policy in thedraft-8
headers.headersDraftVersion
validation check to identifies cases where an unsupported version string is passed to thestandardHeaders
option.You can view the full changelog here.
v7.4.1
Compare Source
Fixed
passOnStoreError
return after callingnext()
rather than continuing execution.You can view the full changelog here.
v7.4.0
Compare Source
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
Compare Source
Fixed
creationStack
validation check when a storewith
localKeys
set to false is used.creationStack
check.You can view the full changelog here.
v7.3.0
Compare Source
Added
unsharedStore
validation check that identifies cases where asingle store instance is shared across multiple limiters.
You can view the full changelog here.
v7.2.0
Compare Source
Added
creationStack
validation check that looks for instances createdin a request handler.
You can view the full changelog here.
v7.1.5
Compare Source
Fixed
async
requestWasSuccessful
methods to work as documented.You can view the full changelog here.
v7.1.4
Compare Source
Fixed
Bun.
You can view the full changelog here.
v7.1.3
Compare Source
Changed
#415)
You can view the full changelog here.
v7.1.2
Compare Source
Changed
documentation website.
You can view the full changelog here.
v7.1.1
Compare Source
Misc
You can view the full changelog here.
v7.1.0
Compare Source
Changed
getKey
method is now always defined. If the store does not have therequired
get
method,getKey
will throw an error explaining this.You can view the full changelog here.
v7.0.2
Compare Source
Added
cluster-memory-store
to the readme and made a couple of other minorclarifications.
You can view the full changelog here.
v7.0.1
Compare Source
Added
rate-limit-postgresql
to thestores
list in the readme.You can view the full changelog here.
v7.0.0
Compare Source
Breaking
max
is set to 0:max: 0
was treated as a 'disable' flag and would allow all requests through.req.rateLimit.current
toreq.rateLimit.used
.current
is now a hidden getter that will return theused
value, but it will not appear when iterating over the keys or callingJSON.stringify()
.express-rate-limit
now targetses2022
in TypeScript/ESBuild.dts-bundle-generator
from v7 to v8.Deprecated
draft_polli_ratelimit_headers
option (it was deprecated in v6).standardHeaders: 'draft-6'
instead.onLimitReached
option (it was deprecated in v6).handler
option.Changed
MemoryStore
now uses precise, per-user reset times rather than a global window that resets all users at once.limit
configuration option is now prefered tomax
.max
is still supported. The change was made to better align with terminology used in the IETF standard drafts.Added
validate
config option can now be an object with keys to enable or disable specific validation checks. For more information, see this.v6.11.2
Compare Source
Fixed
IncrementResponse
TypeScript type (See #397)v6.11.1
Compare Source
Fixed
v6.11.0
Compare Source
Added
v6.10.0
Compare Source
Added
RateLimit
header from the RateLimit header fields for HTTP standardization draft adopted by the IETF. Enable by settingstandardHeaders: 'draft-7'
standardHeaders: 'draft-6'
option, treated equivalent tostandardHeaders: true
from previous releases. (true
andfalse
are still supported.)RateLimit-Policy
header added whenstandardHeaders
is set to'draft-6'
,'draft-7'
, ortrue
draft_polli_ratelimit_headers
optiononLimitReached
optiontotalHits
value returned from Store is invalidv6.9.0
Compare Source
Added
ValidationError
, directing users to the appropriate wiki page for more infoChanged
You can view the full changelog here.
v6.8.1
Compare Source
Changed
You can view the full changelog here.
v6.8.0
Compare Source
Added
https://github.com/express-rate-limit/express-rate-limit/wiki/Error-Codes for
a list of potential errors. Can be disabled by setting
validate: false
inthe configuration. Automatically disables after the first request. (See
#358)
You can view the changelog here.
v6.7.2
Compare Source
(Backport of v6.8.1)
You can view the full changelog here.
v6.7.1
Compare Source
Fixed
node16
moduleresolution strategy (See
#355)
Changed
node
20 to list of versions the CI jobs run on.No functional changes.
You can view the changelog here.
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.
This PR was generated by Mend Renovate. View the repository job log.