jhatler / janus

Just Another Neural Utility System
MIT License
1 stars 3 forks source link

chore(deps-dev): Bump lru-cache from 7.18.3 to 10.3.0 #357

Closed dependabot[bot] closed 1 month ago

dependabot[bot] commented 1 month ago

Bumps lru-cache from 7.18.3 to 10.3.0.

Changelog

Sourced from lru-cache's changelog.

10.3.0

  • add forceFetch() method
  • set disposeReason to 'expire' when it's the result of a TTL expiration, or 'fetch' when it's the result of an aborted or undefined-returning fetch()
  • add memo() method

10.2.0

  • types: implement the Map<K, V> interface

10.1.0

  • add cache.info(key) to get value as well as ttl and size information.

10.0.0

  • cache.fetch() return type is now Promise<V | undefined> instead of Promise<V | void>. This is an irrelevant change practically speaking, but can require changes for TypeScript users.

9.1.0

  • cache.set(key, undefined) is now an alias for cache.delete(key)

9.0.0

  • Use named export only, no default export.
  • Bring back minimal polyfill. If this polyfill ends up being used, then a warning is printed, as it is not safe for use outside of LRUCache.

8.0.0

  • The fetchContext option was renamed to context, and may no longer be set on the cache instance itself.
  • Rewritten in TypeScript, so pretty much all the types moved around a lot.
  • The AbortController/AbortSignal polyfill is removed. For this reason, Node version 16.14.0 or higher is now required.
  • Internal properties were moved to actual private class properties.
  • Keys and values must not be null or undefined.
  • Minified export available at 'lru-cache/min', for both CJS and MJS builds.

... (truncated)

Commits
  • d71af85 10.3.0
  • bad77b9 docs: move all API and options docs into typedocs
  • 4352239 changelog memo() method
  • 40126dd add cache.memo(), options.memoMethod
  • b421c41 changelog 10.3
  • cf8076e set dispose reason to 'expire' when ttl expires
  • 01b4c0c add cache.forceFetch, a fetch() that cannot return undefined
  • aaaa7d7 ttl docs fix
  • a7868fc fix few typos in README.md
  • 200c622 ci: remove makework, update node versions
  • Additional commits viewable in compare view


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot] commented 1 month ago

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.