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

fix(deps): update dependency cache-manager to v5.5.2 #234

Merged
merged 1 commit into from
May 5, 2024
Merged

fix(deps): update dependency cache-manager to v5.5.2 #234

merged 1 commit into from
May 5, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 5, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
cache-manager 5.2.0 -> 5.5.2 age adoption passing confidence

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)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ 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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot enabled auto-merge (rebase) May 5, 2024 16:16
@github-actions GitHub Actions
Copy link

github-actions bot commented May 5, 2024

Coverage report for .

Total coverage

Status Category Percentage Covered / Total
🔴 Statements 9.91% 22/222
🔴 Branches 8.33% 2/24
🔴 Functions 5.88% 2/34
🔴 Lines 8.81% 17/193

Status of coverage: 🟢 - ok, 🟡 - slightly more than threshold, 🔴 - under the threshold

Report generated by 🧪jest coverage report action from 4b02954

@renovate renovate bot merged commit 232a878 into main May 5, 2024
6 checks passed
@renovate renovate bot deleted the renovate/cache-manager-5.x branch May 5, 2024 16:18
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.
0 participants