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.0Release Notes
laminas/laminas-cache (laminas/laminas-cache)
v4.1.0Compare 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.4Compare Source
Release Notes for 4.0.4
4.0.4
Documentation
max&#​95;itemsMemoryadapter option thanks to @boesingFilesystemOptionsrelated toFilesystemv3.0 thanks to @boesingv4.0.3Compare Source
Release Notes for 4.0.3
4.0.3
Bug
v4.0.2Compare Source
Release Notes for 4.0.2
4.0.x bugfix release (patch)
4.0.2
Bug
StorageInterfaceusage thanks to @boesingv4.0.1Compare Source
Release Notes for 4.0.1
4.0.x bugfix release (patch)
4.0.1
Bug
StorageInterfacethanks to @boesingv4.0.0Compare Source
Release Notes for 4.0.0
laminas-cache4.0.0 is here and finally adds native types everywhere, adds support forpsr/cacheandpsr/simple-cachev2 & 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
metadatanow implementsMetadataCapableInterfaceand provides a dedicated object containing all the metadata values it supportspsr/cacheandpsr/simple-cachev2 & v3Removed
supportedMetadatacapability fromCapabilitiesKeyListIterator::CURRENT_AS_METADATAmode along withLaminas\Cache\Exception\MissingKeyExceptionSerializerInterfacewhen callingPluginOptions#getSerializerStorageInterface, so there is no moreStorageInterface#incrementItem,StorageInterface#decrementItem,StorageInterface#decrementItemsandStorageInterface#incrementItemsincrementItem,incrementItems,decrementItem,derementItemsevents (pre,postandexception)laminas/laminas-cache-storage-adapter-implementationwhich now allowslaminas-cacheto be required without a concrete storage adapter implementationpsr/cacheandpsr/simple-cachev1Breaking Changes
AbstractAdapterandStorageInterfaceare not aware of the methodsgetMetadataanymore. These were moved to the newMetadataCapableInterfaceCapabilitiesdo not providesupportedMetadataanymore. 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 anywayKeyListIteratorand the correspondingIteratorInterfacedoes not provide themodeCURRENT_AS_METADATAanymorePluginOptions#getSerializerdoes not create a serializer anymore if astringoption was passed, instead, thestringis returnedStorageInterface, so there is no moreStorageInterface#incrementItem,StorageInterface#decrementItem,StorageInterface#decrementItemsandStorageInterface#incrementItemsincrementItem,incrementItems,decrementItem,derementItemsevents (pre,postandexception)ObjectCachedoes not inherit theCallbackCachepattern anymore4.0.0
BC Break,Enhancement
finalto a bunch of classes thanks to @boesingCapabilitiesas a read-only class thanks to @boesinglaminas/laminas-servicemanagerv4 thanks to @boesingMetadataCapableInterfacethanks to @boesingEnhancement
non-empty-stringthanks to @boesinglaminas/laminas-feeddev-dependency thanks to @boesingvimeo/psalmto v5.20.0 thanks to @boesinglaminas/laminas-cache-storage-implementationthanks to @boesingvimeo/psalmto v5.16 once available thanks to @boesingBug,Enhancement
BC Break,Feature Removal
BC Break
incrementanddecrementfunctionality thanks to @boesingFeature Request
BC Break,Bug
Serializerplugin has to serializetokento enableStorageInterface#checkAndSetItemcomparing the correct values thanks to @boesingDocumentation
laminas/laminas-cache-storage-adapter-filesystem (laminas/laminas-cache-storage-adapter-filesystem)
v3.1.0Compare Source
Release Notes for 3.1.0
Feature release (minor)
This release adds support for PHP 8.4.
3.1.0
Enhancement
v3.0.0Compare Source
Release Notes for 3.0.0
Backwards incompatible release (major)
laminas-cache-storage-adapter-filesystem3.0.0 is here and finally adds native types everywhere, adds support forpsr/cacheandpsr/simple-cachev2 & v3, supportslaminas/laminas-cachev4 and introduces an all new metadata and persistence logic. TheFilesystemdoes now persist the value as a serialized string along with the expiry date so that cache items can now have dedicated TTLs.Added
Metadataobject forFilesystem#getMetadatapsr/cacheandpsr/simple-cachev2 & v3 by introducing TTL per-item handlingFilesystemnow allows passing aClockInterfacevia its constructorunserializable_classes) which can be passed as aFilesystemoption asbooleanor anon-empty-list<class-string>value. Defaults totrueand can be modified according to the unserialize function documentation (value is passed toallowed_classesoption ofunserialize). This option is only used when there is noSerializerplugin attached to the storage adapterFilesystemInteractionInterfacedoes now provide a new methodgetFirstLineOfFileto have a performant way to read the cache expiry information without loading the whole file into memoryChanged
on-writerather thanon-readFilesystemadapter now uses.cachesuffix which is not configurable anymore (used to be.dat) as the old.datfiles 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 upgradingFilesystemOptionsdoes now prevent projects from updating the key pattern, the key pattern is fixed and must not changeFilesystemOptionshas 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.Filesystemadapter now stores values as serialized strings within the cache file in case that there is noSerializerplugin attached to the adapterRemoved
Filesystem::METADATA_ATIMEconstant, useMetadata#lastAccessTimeinsteadFilesystem::METADATA_CTIMEconstant, useMetadata#creationTimeinsteadFilesystem::METADATA_MTIMEconstant, useMetadata#lastModifiedTimeinsteadFilesystem::METADATA_FILESIZEconstant, useMetadata#filesizeinsteadFilesystem::METADATA_FILESPECconstant, useMetadata#filespecinsteadFilesystemOptions#setSuffixas the suffix is not configurable anymoreFilesystemOptions#getSuffixas the suffix is not configurable anymoreFilesystemOptions#setTagSuffixas the tag suffix is not configurable anymoreFilesystemOptions#getTagSuffixas the tag suffix is not configurable anymoreFilesystemInteractionInterface#umaskas it was not usedFilesystemInteractionInterface#touchas it is not used anymore3.0.0
Enhancement
laminas-cache-storage-adapter-testv4.1 thanks to @boesingSerializerplugin is used thanks to @boesingBC Break,Enhancement
laminas-cachev4 thanks to @boesingEnhancement,RFC,Won't Fix
BC Break
laminas/laminas-serializer (laminas/laminas-serializer)
v3.1.0Compare Source
Release Notes for 3.1.0
Feature release (minor)
3.1.0
Enhancement
renovate
v3.0.0Compare 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-servicemanagerv4.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
Wddxadapter.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\Serializeris removed in favor of proper dependency injectionLaminas\Serializer\Adapter\MsgPackis removed to reduce the amount of maintenance within this componentLaminas\Serializer\Adapter\PythonPickleis removed to reduce the amount of maintenance within this componentLaminas\Serializer\Adapter\Wddxis 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\AdapterInterfaceserviceAdded
Laminas\Serializer\GenericSerializerFactoryin case projects want to re-configure the default serializer (PhpSerialize) provided by theLaminas\Serializer\Adapter\AdapterInterfaceservicelaminas/laminas-servicemanagerv4.0.0 and thereforepsr/containerv2.0.03.0.0
Documentation
Enhancement
laminas/laminas-servicemanagerto v4.1.0+ thanks to @boesinglaminas-servicemanagerthanks to @boesingDocumentation,Enhancement
BC Break,Enhancement,Feature Removal
BC Break,Enhancement
laminas-servicemanagerv4.0 thanks to @boesingBC Break,Documentation,Enhancement
BC Break,RFC
MsgPack,PhpCode,PythonPickleandWddxthanks 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.