-
-
Notifications
You must be signed in to change notification settings - Fork 82
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
fix(deps): update dependency cache-manager to v5 - autoclosed #2571
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
added
[status] needs review
PRs that are ready to be reviewed.
[type] chore
labels
Sep 29, 2022
renovate
bot
force-pushed
the
renovate/cache-manager-5.x
branch
4 times, most recently
from
October 9, 2022 22:27
3083610
to
95a090a
Compare
renovate
bot
force-pushed
the
renovate/cache-manager-5.x
branch
5 times, most recently
from
October 25, 2022 06:15
879ecdd
to
3e2f218
Compare
renovate
bot
force-pushed
the
renovate/cache-manager-5.x
branch
4 times, most recently
from
November 2, 2022 16:05
7704d1b
to
8457e41
Compare
renovate
bot
force-pushed
the
renovate/cache-manager-5.x
branch
from
November 7, 2022 23:38
8457e41
to
2aacda9
Compare
renovate
bot
force-pushed
the
renovate/cache-manager-5.x
branch
3 times, most recently
from
November 21, 2022 22:47
ec3620f
to
4007a43
Compare
renovate
bot
force-pushed
the
renovate/cache-manager-5.x
branch
2 times, most recently
from
December 4, 2022 16:05
dc10bc1
to
e90e745
Compare
renovate
bot
force-pushed
the
renovate/cache-manager-5.x
branch
3 times, most recently
from
December 12, 2022 21:03
8f7555f
to
68e08c9
Compare
renovate
bot
force-pushed
the
renovate/cache-manager-5.x
branch
2 times, most recently
from
December 26, 2022 22:32
d56494a
to
9774089
Compare
renovate
bot
force-pushed
the
renovate/cache-manager-5.x
branch
4 times, most recently
from
January 9, 2023 16:05
b88f1a3
to
e8dd22b
Compare
renovate
bot
force-pushed
the
renovate/cache-manager-5.x
branch
from
June 19, 2023 03:10
0db85e2
to
a4ac018
Compare
renovate
bot
force-pushed
the
renovate/cache-manager-5.x
branch
from
July 26, 2023 14:48
a4ac018
to
88c559e
Compare
renovate
bot
force-pushed
the
renovate/cache-manager-5.x
branch
2 times, most recently
from
October 10, 2023 13:38
33b9c28
to
59e65bd
Compare
renovate
bot
force-pushed
the
renovate/cache-manager-5.x
branch
2 times, most recently
from
October 16, 2023 03:32
66770f6
to
892ac1c
Compare
renovate
bot
force-pushed
the
renovate/cache-manager-5.x
branch
2 times, most recently
from
November 17, 2023 15:54
af3be96
to
11ad50d
Compare
renovate
bot
force-pushed
the
renovate/cache-manager-5.x
branch
from
December 19, 2023 17:15
11ad50d
to
bd1e4d1
Compare
renovate
bot
force-pushed
the
renovate/cache-manager-5.x
branch
from
January 20, 2024 02:04
bd1e4d1
to
7607a0c
Compare
renovate
bot
force-pushed
the
renovate/cache-manager-5.x
branch
2 times, most recently
from
April 5, 2024 20:15
0b21240
to
4bbcea5
Compare
renovate
bot
force-pushed
the
renovate/cache-manager-5.x
branch
from
April 29, 2024 16:02
4bbcea5
to
bbb31c3
Compare
renovate
bot
force-pushed
the
renovate/cache-manager-5.x
branch
from
May 23, 2024 02:17
bbb31c3
to
490337a
Compare
renovate
bot
force-pushed
the
renovate/cache-manager-5.x
branch
2 times, most recently
from
June 5, 2024 18:28
0df3b9d
to
d903c4e
Compare
renovate
bot
force-pushed
the
renovate/cache-manager-5.x
branch
3 times, most recently
from
June 20, 2024 22:33
a5e10f4
to
ccf8ad0
Compare
renovate
bot
force-pushed
the
renovate/cache-manager-5.x
branch
4 times, most recently
from
July 15, 2024 18:03
30b9886
to
5d0ddcc
Compare
renovate
bot
force-pushed
the
renovate/cache-manager-5.x
branch
from
July 28, 2024 17:04
5d0ddcc
to
2a13aba
Compare
renovate
bot
force-pushed
the
renovate/cache-manager-5.x
branch
from
August 5, 2024 23:23
2a13aba
to
f3f55a0
Compare
renovate
bot
force-pushed
the
renovate/cache-manager-5.x
branch
from
August 6, 2024 22:16
f3f55a0
to
cbd4567
Compare
renovate
bot
changed the title
fix(deps): update dependency cache-manager to v5
fix(deps): update dependency cache-manager to v5 - autoclosed
Sep 23, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
^4.0.0
->^5.0.0
4.1.0
->5.7.6
Release Notes
jaredwray/cacheable (cache-manager)
v5.5.0
Compare Source
Added Event Errors
Cache Manager now does not throw errors by default. Instead, all errors are evented through the error event. Here is an example on how to use it:
What's Changed
New Contributors
Full Changelog: jaredwray/cacheable@v5.4.0...v5.5.0
v5.4.0
Compare Source
Refresh cache keys in background
Both the caching and multicaching modules support a mechanism to refresh expiring cache keys in background when using the
wrap
function.This is done by adding a
refreshThreshold
attribute while creating the caching store or passing it to the wrap function.If
refreshThreshold
is set and after retrieving a value from cache the TTL will be checked.If the remaining TTL is less than refreshThreshold, the system will update the value asynchronously,
following same rules as standard fetching. In the meantime, the system will return the old value until expiration.
What's Changed
Full Changelog: jaredwray/cacheable@v5.3.2...v5.4.0
v5.3.2
Compare Source
What's Changed
New Contributors
Full Changelog: jaredwray/cacheable@v5.3.0...v5.3.2
v5.3.1
Compare Source
Major fix as
5.3.0
did not have the dist folder on release.What's Changed
wrap
function by @douglascayers in https://github.com/node-cache-manager/node-cache-manager/pull/599New Contributors
Full Changelog: jaredwray/cacheable@5.2.4...v5.3.1
v5.3.0
Compare Source
What's Changed
wrap
function by @douglascayers in https://github.com/node-cache-manager/node-cache-manager/pull/599New Contributors
Full Changelog: jaredwray/cacheable@5.2.4...v5.3.0
v5.2.4
Compare Source
Updates 🍻
async <T>(key: string, fn: () => Promise<T>, ttl?: WrapTTL<T>)
- https://github.com/node-cache-manager/node-cache-manager/pull/535What's Changed
New Contributors
Full Changelog: jaredwray/cacheable@5.2.3...5.2.4
v5.2.3
Compare Source
Bug Fixes
v5.2.2
Compare Source
Bug Fixes
v5.2.1
Compare Source
Bug Fixes
v5.2.0
Compare Source
Bug Fixes
Features
v5.1.7
Compare Source
Bug Fixes
v5.1.6
Compare Source
Bug Fixes
v5.1.5
Compare Source
Bug Fixes
v5.1.4
Compare Source
Bug Fixes
v5.1.3
Compare Source
Bug Fixes
v5.1.2
Compare Source
Bug Fixes
v5.1.1
Compare Source
Bug Fixes
v5.1.0
Compare Source
Features
v5.0.1
Compare Source
v5.0.0
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 these updates again.
This PR was generated by Mend Renovate. View the repository job log.