ipregistry / ipregistry-javascript

Official Javascript Client for Ipregistry: a Non-Intrusive Solution for IP Geolocation and Threat Data.
https://ipregistry.co
Apache License 2.0
17 stars 3 forks source link

Bump lru-cache from 9.0.1 to 10.0.0 #308

Closed dependabot[bot] closed 8 months ago

dependabot[bot] commented 1 year ago

Bumps lru-cache from 9.0.1 to 10.0.0.

Changelog

Sourced from lru-cache's changelog.

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.

7.18.0

  • Add support for internal state investigation through the use of a status option to has(), set(), get(), and fetch().

7.17.0

  • Add signal option for fetch to pass a user-supplied AbortSignal
  • Add ignoreFetchAbort and allowStaleOnFetchAbort options

7.16.2

  • Fail fetch() promises when they are aborted

7.16.0

... (truncated)

Commits
  • c5ca277 10.0.0
  • ca4ea17 fetch resolve to undefined rather than void
  • 01075cb 9.1.2
  • 80ab1cd update @​types/node, docs on allowStaleOnFetchAbort
  • df2451d add node 20 to ci, workarounds for ts-node loader failing on node 20
  • 7d51bb3 9.1.1
  • 3a71a30 Correct remainingTTL reported on status object
  • 4134a83 9.1.0
  • db6c2ec cache.set(k, undefined) alias to cache.delete(k)
  • 88bb31c 9.0.3
  • 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 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 8 months 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.