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.

Sign up for GitHub

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

Jump to bottom

Update dependency cache-manager to v5 #1677

Closed
wants to merge 1 commit into from
Closed

Update dependency cache-manager to v5 #1677

wants to merge 1 commit into from

Conversation

balena-renovate[bot]
Copy link
Contributor

@balena-renovate balena-renovate bot commented Jun 19, 2024 •
edited
Loading

This PR contains the following updates:

Package Type Update Change
cache-manager dependencies major ^4.1.0 -> ^5.0.0

Release Notes

jaredwray/cache-manager (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:

const memoryCache = await caching('memory', {
  max: 100,
  ttl: 10 * 1000 /*milliseconds*/,
});
memoryCache.on('error', (error) => {
  console.error('Cache error:', error);
});

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

New Contributors

Full Changelog: jaredwray/cacheable@5.2.4...v5.3.1

v5.3.0

Compare Source

What's Changed

New Contributors

Full Changelog: jaredwray/cacheable@5.2.4...v5.3.0

v5.2.4

Compare Source

Updates 🍻

What'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
  • deps: update dependency lru-cache to ~9.1.0 (d9ec046)
  • deps: update dependency lru-cache to v9 (fde0015)
  • update lru-cache (87efeff)

v5.2.0

Compare Source

Bug Fixes
  • multi-caching: minor issues (bf68d36)
Features

v5.1.7

Compare Source

Bug Fixes
  • lru-cache breaking changes (8398494)

v5.1.6

Compare Source

Bug Fixes

v5.1.5

Compare Source

Bug Fixes
  • rename type alias Ttl as Milliseconds (daa5fa8)

v5.1.4

Compare Source

Bug Fixes

v5.1.3

Compare Source

Bug Fixes
  • example multichaching in README (e01f780)
  • parallelize set higher priority at wrap (7f76e54)

v5.1.2

Compare Source

Bug Fixes
  • links to ioredis in Readme (1ba46d8)
  • re populate higher priority caches when a key is found in lower ones (7a6a10c)

v5.1.1

Compare Source

Bug Fixes
  • bad Cache definition (3746c39)
  • mget/mset examples in README (1ca67a4)

v5.1.0

Compare Source

Features
  • add ttl argument in wrap method (b06c1e5)

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

@balena-renovate balena-renovate bot force-pushed the renovate/major-5-cache-manager branch 8 times, most recently from 7f7a56e to be45095 Compare June 26, 2024 12:59
@balena-renovate balena-renovate bot force-pushed the renovate/major-5-cache-manager branch 11 times, most recently from 5899818 to 7311fb5 Compare July 4, 2024 13:01
@balena-renovate balena-renovate bot force-pushed the renovate/major-5-cache-manager branch 10 times, most recently from 73338d8 to 06ea34a Compare July 10, 2024 19:56
@balena-renovate balena-renovate bot force-pushed the renovate/major-5-cache-manager branch 3 times, most recently from db1b3f0 to df68b17 Compare July 15, 2024 02:14
@balena-renovate
Update dependency cache-manager to v5
e8f320d 
Update cache-manager from 4.1.0 to 5.7.2

Change-type: patch
@balena-renovate balena-renovate bot force-pushed the renovate/major-5-cache-manager branch from df68b17 to e8f320d Compare July 15, 2024 07:55
@thgreasi thgreasi closed this Jul 15, 2024
@balena-renovate balena-renovate
Copy link
Contributor Author

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 5.x releases. But if you manually upgrade to 5.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@balena-renovate balena-renovate bot deleted the renovate/major-5-cache-manager branch July 15, 2024 16:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
renovate
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@thgreasi