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.7.6 - autoclosed #15

Closed
wants to merge 1 commit into from
Closed

Update dependency cache-manager to v5.7.6 - autoclosed #15

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 19, 2024 •
edited by w3bdesign
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
cache-manager (source) 5.2.3 -> 5.7.6 age adoption passing confidence

Release Notes

jaredwray/cacheable (cache-manager)

v5.5.0

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

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

What's Changed

New Contributors

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

v5.3.1

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

What's Changed

New Contributors

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

v5.2.4

Updates 🍻

What's Changed

New Contributors

Full Changelog: jaredwray/cacheable@5.2.3...5.2.4

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.

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

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/cache-manager-5.x branch from 09ef531 to 2b6b18c Compare November 19, 2024 16:40
@renovate renovate bot force-pushed the renovate/cache-manager-5.x branch from 3cb5474 to 633def6 Compare November 20, 2024 03:17
@codecov-commenter
Copy link

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 94.77%. Comparing base (f933014) to head (633def6).

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             main      #15   +/-   ##
=======================================
  Coverage   94.77%   94.77%           
=======================================
  Files          45       45           
  Lines         689      689           
  Branches       50       50           
=======================================
  Hits          653      653           
- Misses         35       36    +1     
+ Partials        1        0    -1
Flag Coverage Δ
backend 94.77% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

see 1 file with indirect coverage changes

---- 🚨 Try these New Features:

@renovate renovate bot changed the title Update dependency cache-manager to v5.7.6 Update dependency cache-manager to v5.7.6 - autoclosed Nov 20, 2024
@renovate renovate bot closed this Nov 20, 2024
@renovate renovate bot deleted the renovate/cache-manager-5.x branch November 20, 2024 03:21
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
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@codecov-commenter