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

Update dependency lru-cache to v7.18.3 #69

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 16, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
lru-cache 7.13.2 -> 7.18.3 age adoption passing confidence

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

  • Add support for internal state investigation through the use of
    a status option to has(), set(), get(), and fetch().

v7.17.2

Compare Source

v7.17.1

Compare Source

v7.17.0

Compare Source

  • Add signal option for fetch to pass a user-supplied
    AbortSignal
  • Add ignoreFetchAbort and allowStaleOnFetchAbort options

v7.16.2

Compare Source

  • Fail fetch() promises when they are aborted

v7.16.1

Compare Source

v7.16.0

Compare Source

  • Add allowStaleOnFetchRejection option

v7.15.0

Compare Source

  • Provide both ESM and CommonJS exports

v7.14.1

Compare Source

v7.14.0

Compare Source

  • Add maxEntrySize option to prevent caching items above a
    given calculated size.

Configuration

📅 Schedule: Branch creation - "after 10am and before 6pm every weekday" in timezone Europe/Berlin, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/lru-cache-7.x-lockfile branch 18 times, most recently from 70f9eec to 3672f78 Compare March 23, 2023 13:30
@renovate renovate bot force-pushed the renovate/lru-cache-7.x-lockfile branch 10 times, most recently from 4d6f7b1 to f9cfd21 Compare March 31, 2023 10:24
@renovate renovate bot force-pushed the renovate/lru-cache-7.x-lockfile branch 2 times, most recently from 50aac15 to a2d61c9 Compare April 10, 2023 13:39
@renovate renovate bot force-pushed the renovate/lru-cache-7.x-lockfile branch 5 times, most recently from 7d65cf3 to b298a73 Compare January 30, 2024 12:18
@renovate renovate bot force-pushed the renovate/lru-cache-7.x-lockfile branch 7 times, most recently from 50ec1c5 to 428dc06 Compare February 7, 2024 16:08
@renovate renovate bot force-pushed the renovate/lru-cache-7.x-lockfile branch from 428dc06 to 4ae7a05 Compare February 14, 2024 13:10
@renovate renovate bot force-pushed the renovate/lru-cache-7.x-lockfile branch 2 times, most recently from eb54f49 to 7e23a93 Compare February 21, 2024 14:57
@renovate renovate bot force-pushed the renovate/lru-cache-7.x-lockfile branch 4 times, most recently from 89ba5ae to f84b63a Compare March 11, 2024 13:51
@renovate renovate bot force-pushed the renovate/lru-cache-7.x-lockfile branch 3 times, most recently from 54dc3c4 to 45e9d45 Compare March 29, 2024 00:46
@renovate renovate bot force-pushed the renovate/lru-cache-7.x-lockfile branch 4 times, most recently from 5289ab8 to bad9319 Compare April 16, 2024 13:14
@renovate renovate bot force-pushed the renovate/lru-cache-7.x-lockfile branch 2 times, most recently from 1682280 to 6e3f9c4 Compare May 28, 2024 08:14
@renovate renovate bot force-pushed the renovate/lru-cache-7.x-lockfile branch from 6e3f9c4 to 2f91015 Compare July 4, 2024 17:27
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

0 participants