Update dependency lru-cache to v7.18.3 - test rename #11447
Closed
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.
https://jira.dev.bbc.co.uk/browse/NEWSWORLDSERVICE-1947
This PR contains the following updates:
7.7.1
->7.18.3
Release Notes
isaacs/node-lru-cache (lru-cache)
v7.18.3
Compare Source
v7.18.2
Compare Source
v7.18.1
Compare Source
v7.18.0
Compare Source
a
status
option tohas()
,set()
,get()
, andfetch()
.v7.17.2
Compare Source
v7.17.1
Compare Source
v7.17.0
Compare Source
signal
option forfetch
to pass a user-suppliedAbortSignal
ignoreFetchAbort
andallowStaleOnFetchAbort
optionsv7.16.2
Compare Source
v7.16.1
Compare Source
v7.16.0
Compare Source
allowStaleOnFetchRejection
optionv7.15.0
Compare Source
v7.14.1
Compare Source
v7.14.0
Compare Source
maxEntrySize
option to prevent caching items above agiven calculated size.
v7.13.2
Compare Source
v7.13.1
Compare Source
v7.13.0
Compare Source
forceRefresh
option to trigger a call to thefetchMethod
even if the item is found in cache, and notolder than its
ttl
.v7.12.1
Compare Source
v7.12.0
Compare Source
fetchContext
option to provide additional information tothe
fetchMethod
maxSize
would cause bizarre behavior.v7.11.0
Compare Source
get()
of a stale item would remove it from the cache.v7.10.3
Compare Source
v7.10.2
Compare Source
v7.10.1
Compare Source
v7.10.0
Compare Source
noDeleteOnFetchRejection
option, to suppress behaviorwhere a failed
fetch
will delete a previous stale value.out of date types coming from DefinitelyTyped.
v7.9.1
Compare Source
v7.9.0
Compare Source
signal.addEventListener('abort')
andsignal.onabort
.unhandledRejection
when thefetchMethod
throws an error orreturns a rejected Promise.
v7.8.2
Compare Source
v7.8.1
Compare Source
v7.8.0
Compare Source
updateAgeOnHas
optionconsole.error
ifprocess.emitWarning
unavailablev7.7.4
Compare Source
v7.7.3
Compare Source
v7.7.2
Compare Source
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 has been generated by Mend Renovate. View repository job log here.