fix(deps): update dependency cache-manager to v5.3.2

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
cache-manager	5.3.1 -> 5.3.2

---

Release Notes

node-cache-manager/node-cache-manager (cache-manager)

v5.3.2

Compare Source

What's Changed

• Use a github action workflow to release new versions by @​QuentinLemCode in https://github.com/node-cache-manager/node-cache-manager/pull/612
• adding in prepare for the build by @​jaredwray in https://github.com/node-cache-manager/node-cache-manager/pull/618
• fix: exclude sourcemap when package publish by @​czy88840616 in https://github.com/node-cache-manager/node-cache-manager/pull/622
• updating clean to scripts by @​jaredwray in https://github.com/node-cache-manager/node-cache-manager/pull/623
• feat: support sync cache creation by @​denkan in https://github.com/node-cache-manager/node-cache-manager/pull/598
• 619: Ensure that background refresh only calls fn once. by @​ricall in https://github.com/node-cache-manager/node-cache-manager/pull/620
• updating typescript and removing release workflow by @​jaredwray in https://github.com/node-cache-manager/node-cache-manager/pull/624
• updating vitest to 1.1.0 by @​jaredwray in https://github.com/node-cache-manager/node-cache-manager/pull/625
• upgrading promise-coalesce to 1.1.2 by @​jaredwray in https://github.com/node-cache-manager/node-cache-manager/pull/626
• upgrading lru-cache to 10.1.0 by @​jaredwray in https://github.com/node-cache-manager/node-cache-manager/pull/627
• upgrading typescript and eslint to latest by @​jaredwray in https://github.com/node-cache-manager/node-cache-manager/pull/628

New Contributors

• @​QuentinLemCode made their first contribution in https://github.com/node-cache-manager/node-cache-manager/pull/612
• @​czy88840616 made their first contribution in https://github.com/node-cache-manager/node-cache-manager/pull/622
• @​denkan made their first contribution in https://github.com/node-cache-manager/node-cache-manager/pull/598
• @​ricall made their first contribution in https://github.com/node-cache-manager/node-cache-manager/pull/620

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

---

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

[semanticdiff-com]

Review changes with SemanticDiff.

Analyzed 1 of 1 files.

	Filename	Status
✔️	package-lock.json	27.23% smaller

[restack-app]

No applications have been configured for previews targeting branch: master. To do so go to restack console and configure your applications for previews.

[coderabbitai]

Important

Auto Review Skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on X ?

---

Tips

Chat with CodeRabbit Bot (@coderabbitai)

• You can reply to a review comment made by CodeRabbit.
• You can tag CodeRabbit on specific lines of code or files in the PR by tagging @coderabbitai in a comment.
• You can tag @coderabbitai in a PR comment and ask one-off questions about the PR and the codebase. Use quoted replies to pass the context for follow-up questions.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

[pr-code-reviewer]

👋 Hi there!

The most important things to improve in the given code-diff are:

1. Update the version of "cache-manager" from 5.3.1 to 5.3.2.
2. Update the version of "lru-cache" from 10.0.2 to 10.1.0.
3. Update the version of "promise-coalesce" from 1.1.1 to 1.1.2.

_{^{Automatically generated with the help of gpt-3.5-turbo.
Feedback? Please don't hesitate to drop me an email at webber@takken.io.}}

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Pages

Latest commit:	964c4b9
Status:	✅  Deploy successful!
Preview URL:	https://0fe2d62f.automation-app-bot.pages.dev
Branch Preview URL:	https://renovate-cache-manager-5-x-l.automation-app-bot.pages.dev

View logs

[instapr]

The pull request is updating the cache-manager package from 5.3.1 to 5.3.2. The changes in this update include:

• Use a GitHub action workflow to release new versions
• Adding in prepare for the build
• Fixing exclusion of sourcemap when package is published
• Updating clean to scripts
• Adding support for sync cache creation
• Ensuring that background refresh only calls the function once
• Updating typescript and removing release workflow
• Updating vitest to version 1.1.0
• Upgrading promise-coalesce to version 1.1.2
• Upgrading lru-cache to version 10.1.0
• Upgrading typescript and eslint to latest

Please review the changes and merge the pull request once you are satisfied.

[sonarqubecloud]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[sweep-ai-deprecated]

Apply Sweep Rules to your PR?

• Apply: All new business logic should have corresponding unit tests.
• Apply: Refactor large functions to be more modular.
• Apply: Add docstrings to all functions and file headers.

[mergeable]

⚠️

Please add Jira ticket id i.e. "JIRA-ID"

Check Fail Adhere to the branch naming convention described here