fix(deps): update laminas packages (major) #20
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:
^3.0
->^4.0
^2.0
->^3.0
^2.10
->^3.0
Release Notes
laminas/laminas-cache (laminas/laminas-cache)
v4.1.0
Compare Source
Release Notes for 4.1.0
Feature release (minor)
This release adds support for PHP 8.4.
4.1.0
Dependencies,Enhancement
Dependencies,Enhancement,QA
Documentation,QA
Enhancement
renovate
v4.0.4
Compare Source
Release Notes for 4.0.4
4.0.4
Documentation
max&#​95;items
Memory
adapter option thanks to @boesingFilesystemOptions
related toFilesystem
v3.0 thanks to @boesingv4.0.3
Compare Source
Release Notes for 4.0.3
4.0.3
Bug
v4.0.2
Compare Source
Release Notes for 4.0.2
4.0.x bugfix release (patch)
4.0.2
Bug
StorageInterface
usage thanks to @boesingv4.0.1
Compare Source
Release Notes for 4.0.1
4.0.x bugfix release (patch)
4.0.1
Bug
StorageInterface
thanks to @boesingv4.0.0
Compare Source
Release Notes for 4.0.0
laminas-cache
4.0.0 is here and finally adds native types everywhere, adds support forpsr/cache
andpsr/simple-cache
v2 & v3 and introduces an all new metadata logic which allows adapters to provide metadata they actually support.Please read more on how to migrate your project in our migration guideline.
Added
metadata
now implementsMetadataCapableInterface
and provides a dedicated object containing all the metadata values it supportspsr/cache
andpsr/simple-cache
v2 & v3Removed
supportedMetadata
capability fromCapabilities
KeyListIterator::CURRENT_AS_METADATA
mode along withLaminas\Cache\Exception\MissingKeyException
SerializerInterface
when callingPluginOptions#getSerializer
StorageInterface
, so there is no moreStorageInterface#incrementItem
,StorageInterface#decrementItem
,StorageInterface#decrementItems
andStorageInterface#incrementItems
incrementItem
,incrementItems
,decrementItem
,derementItems
events (pre
,post
andexception
)laminas/laminas-cache-storage-adapter-implementation
which now allowslaminas-cache
to be required without a concrete storage adapter implementationpsr/cache
andpsr/simple-cache
v1Breaking Changes
AbstractAdapter
andStorageInterface
are not aware of the methodsgetMetadata
anymore. These were moved to the newMetadataCapableInterface
Capabilities
do not providesupportedMetadata
anymore. The supported metadata is tied to the used storage adapter and thus, was already requiring projects to explicitly know the exact implementation of the cache backend in case of using these metadatas anywayKeyListIterator
and the correspondingIteratorInterface
does not provide themode
CURRENT_AS_METADATA
anymorePluginOptions#getSerializer
does not create a serializer anymore if astring
option was passed, instead, thestring
is returnedStorageInterface
, so there is no moreStorageInterface#incrementItem
,StorageInterface#decrementItem
,StorageInterface#decrementItems
andStorageInterface#incrementItems
incrementItem
,incrementItems
,decrementItem
,derementItems
events (pre
,post
andexception
)ObjectCache
does not inherit theCallbackCache
pattern anymore4.0.0
BC Break,Enhancement
final
to a bunch of classes thanks to @boesingCapabilities
as a read-only class thanks to @boesinglaminas/laminas-servicemanager
v4 thanks to @boesingMetadataCapableInterface
thanks to @boesingEnhancement
non-empty-string
thanks to @boesinglaminas/laminas-feed
dev-dependency thanks to @boesingvimeo/psalm
to v5.20.0 thanks to @boesinglaminas/laminas-cache-storage-implementation
thanks to @boesingvimeo/psalm
to v5.16 once available thanks to @boesingBug,Enhancement
BC Break,Feature Removal
BC Break
increment
anddecrement
functionality thanks to @boesingFeature Request
BC Break,Bug
Serializer
plugin has to serializetoken
to enableStorageInterface#checkAndSetItem
comparing the correct values thanks to @boesingDocumentation
laminas/laminas-cache-storage-adapter-filesystem (laminas/laminas-cache-storage-adapter-filesystem)
v3.1.0
Compare Source
Release Notes for 3.1.0
Feature release (minor)
This release adds support for PHP 8.4.
3.1.0
Enhancement
v3.0.0
Compare Source
Release Notes for 3.0.0
Backwards incompatible release (major)
laminas-cache-storage-adapter-filesystem
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 persistence logic. TheFilesystem
does now persist the value as a serialized string along with the expiry date so that cache items can now have dedicated TTLs.Added
Metadata
object forFilesystem#getMetadata
psr/cache
andpsr/simple-cache
v2 & v3 by introducing TTL per-item handlingFilesystem
now allows passing aClockInterface
via its constructorunserializable_classes
) which can be passed as aFilesystem
option asboolean
or anon-empty-list<class-string>
value. Defaults totrue
and can be modified according to the unserialize function documentation (value is passed toallowed_classes
option ofunserialize
). This option is only used when there is noSerializer
plugin attached to the storage adapterFilesystemInteractionInterface
does now provide a new methodgetFirstLineOfFile
to have a performant way to read the cache expiry information without loading the whole file into memoryChanged
on-write
rather thanon-read
Filesystem
adapter now uses.cache
suffix which is not configurable anymore (used to be.dat
) as the old.dat
files might not be compatible anymore. This will probably introduce problems in projects which rely on existing files which are not generated when these are missing. It is also mandatory that if caches are created cross-project, that both projects use the same adapter version. Please keep this in mind when upgradingFilesystemOptions
does now prevent projects from updating the key pattern, the key pattern is fixed and must not changeFilesystemOptions
has a modified key pattern and now allows dots (.
) in cache keys. This is mandatory to have proper PSR-6 support which requires caches to supportA-Z
,a-z
,0-9
,_
, and.
Filesystem
adapter now stores values as serialized strings within the cache file in case that there is noSerializer
plugin attached to the adapterRemoved
Filesystem::METADATA_ATIME
constant, useMetadata#lastAccessTime
insteadFilesystem::METADATA_CTIME
constant, useMetadata#creationTime
insteadFilesystem::METADATA_MTIME
constant, useMetadata#lastModifiedTime
insteadFilesystem::METADATA_FILESIZE
constant, useMetadata#filesize
insteadFilesystem::METADATA_FILESPEC
constant, useMetadata#filespec
insteadFilesystemOptions#setSuffix
as the suffix is not configurable anymoreFilesystemOptions#getSuffix
as the suffix is not configurable anymoreFilesystemOptions#setTagSuffix
as the tag suffix is not configurable anymoreFilesystemOptions#getTagSuffix
as the tag suffix is not configurable anymoreFilesystemInteractionInterface#umask
as it was not usedFilesystemInteractionInterface#touch
as it is not used anymore3.0.0
Enhancement
laminas-cache-storage-adapter-test
v4.1 thanks to @boesingSerializer
plugin is used thanks to @boesingBC Break,Enhancement
laminas-cache
v4 thanks to @boesingEnhancement,RFC,Won't Fix
BC Break
laminas/laminas-serializer (laminas/laminas-serializer)
v3.1.0
Compare Source
Release Notes for 3.1.0
Feature release (minor)
3.1.0
Enhancement
renovate
v3.0.0
Compare Source
Release Notes for 3.0.0
Backwards incompatible release (major)
With v3.0.0, a huge maintenance release is rolled out.
Every property and every method is now fully typed, starting with method arguments up to object properties.
These kind of changes were necessary due to the changes in
laminas-servicemanager
v4.0.0 which is also fully typed starting with v4.0.To reduce further maintenance effort, some niche serializers were dropped in favor or faster CI pipelines and due to the lack of cross-platform checks. Laminas wants to provide fully tested code which was not properly possible for at least the
Wddx
adapter.The migration guide is available on the documentation website:
https://docs.laminas.dev/laminas-serializer/v3/migration/to-version-3/
Breaking Changes
Removed
Laminas\Serializer\Serializer
is removed in favor of proper dependency injectionLaminas\Serializer\Adapter\MsgPack
is removed to reduce the amount of maintenance within this componentLaminas\Serializer\Adapter\PythonPickle
is removed to reduce the amount of maintenance within this componentLaminas\Serializer\Adapter\Wddx
is removed to reduce the amount of maintenance within this componentChanged
Laminas\Serializer\Serializer
, projects now have to either instantiate the default serializer implementation or inject it by consuming theLaminas\Serializer\Adapter\AdapterInterface
serviceAdded
Laminas\Serializer\GenericSerializerFactory
in case projects want to re-configure the default serializer (PhpSerialize
) provided by theLaminas\Serializer\Adapter\AdapterInterface
servicelaminas/laminas-servicemanager
v4.0.0 and thereforepsr/container
v2.0.03.0.0
Documentation
Enhancement
laminas/laminas-servicemanager
to v4.1.0+ thanks to @boesinglaminas-servicemanager
thanks to @boesingDocumentation,Enhancement
BC Break,Enhancement,Feature Removal
BC Break,Enhancement
laminas-servicemanager
v4.0 thanks to @boesingBC Break,Documentation,Enhancement
BC Break,RFC
MsgPack
,PhpCode
,PythonPickle
andWddx
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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot.