Update dependency laminas/laminas-cache-storage-adapter-memory to v3 (master) - autoclosed #110
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^2.0
->^3.0
Release Notes
laminas/laminas-cache-storage-adapter-memory (laminas/laminas-cache-storage-adapter-memory)
v3.0.0
Compare Source
Release Notes for 3.0.0
Backwards incompatible release (major)
laminas-cache-storage-adapter-memory
3.0.0 is here and finally adds native types everywhere, adds support forpsr/cache
andpsr/simple-cache
v2 & v3, supportslaminas/laminas-cache
v4 and introduces an all new metadata and internal persistence logic.The
Memory
adapter had its flaws by juggling with thememory_limit
. There were a bunch of issues with that behavior, especially since it is impossible to calculate the exact free memory available. For more details, one can check #57. With this version, we are introducingmax_items
which limits the amount of items persisted to theMemory
adapter (defaults to unlimited). Once themax_items
are exceeding, the adapter automatically removes the oldest entries to make room for new items.Added
Metadata
object forMemory#getMetadata
psr/cache
andpsr/simple-cache
v2 & v3Memory
now allows passing aClockInterface
via its constructorMemoryOptions
now hasmax_items
configuration to limit the amount of items to be cached. When the limit exceeds, the adapter automatically drops older itemsChanged
on-write
rather thanon-read
max_items
option which can be used to limit the amount of items persisted to the cacheRemoved
MemoryOptions#setMemoryLimit
, there is no replacement. It is recommended to use themax_items
option insteadMemoryOptions#getMemoryLimit
, there is no relacement3.0.0
renovate
RFC
Enhancement
BC Break,Bug,Enhancement
memory&#​95;limit
withmax&#​95;items
thanks to @boesingBC Break,Bug
laminas/laminas-cache
v4 thanks to @boesingConfiguration
📅 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.
This PR was generated by Mend Renovate. View the repository job log.