Update Laminas packages to v4 (major) - #119
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
Contributor
Author
⚠ Artifact update problemRenovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is. ♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
The artifact failure details are included below: File name: composer.lock |
renovate
Bot
force-pushed
the
renovate/major-laminas
branch
2 times, most recently
from
March 15, 2024 12:50
60387a9 to
d99fb00
Compare
renovate
Bot
force-pushed
the
renovate/major-laminas
branch
2 times, most recently
from
March 25, 2024 03:22
9b9cd99 to
483aff5
Compare
renovate
Bot
force-pushed
the
renovate/major-laminas
branch
from
April 1, 2024 03:42
483aff5 to
6333147
Compare
renovate
Bot
force-pushed
the
renovate/major-laminas
branch
2 times, most recently
from
April 15, 2024 03:52
ec68c49 to
7e722cc
Compare
renovate
Bot
force-pushed
the
renovate/major-laminas
branch
from
April 22, 2024 03:23
7e722cc to
4bf19bd
Compare
renovate
Bot
force-pushed
the
renovate/major-laminas
branch
2 times, most recently
from
May 6, 2024 04:24
1e568e9 to
0dd99e1
Compare
renovate
Bot
force-pushed
the
renovate/major-laminas
branch
from
May 13, 2024 03:49
0dd99e1 to
b5b4449
Compare
Contributor
Author
|
renovate
Bot
force-pushed
the
renovate/major-laminas
branch
2 times, most recently
from
May 27, 2024 03:34
65b8091 to
6f30c34
Compare
renovate
Bot
force-pushed
the
renovate/major-laminas
branch
2 times, most recently
from
June 10, 2024 03:45
3344c26 to
c4e49bb
Compare
renovate
Bot
force-pushed
the
renovate/major-laminas
branch
from
June 16, 2024 19:05
c4e49bb to
43a28e2
Compare
| datasource | package | from | to | | ---------- | ------------------------------ | ------ | ----- | | packagist | laminas/laminas-cache | 3.12.2 | 4.0.0 | | packagist | laminas/laminas-servicemanager | 3.22.1 | 4.1.0 | Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
renovate
Bot
force-pushed
the
renovate/major-laminas
branch
from
June 17, 2024 03:19
43a28e2 to
7d7ab3e
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.12.1->^4.0.0^3.21.0->^3.21.0 || ^4.0.0Release Notes
laminas/laminas-cache (laminas/laminas-cache)
v4.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-servicemanager (laminas/laminas-servicemanager)
v4.1.0Compare Source
Release Notes for 4.1.0
Feature release (minor)
4.1.0
Documentation
Documentation,Enhancement
ServiceLocatorInterface#get()generic thanks to @InvisibleSmileyv4.0.2Compare Source
Release Notes for 4.0.2
4.0.x bugfix release (patch)
4.0.2
Bug,Documentation
v4.0.1Compare Source
Release Notes for 4.0.1
4.0.x bugfix release (patch)
4.0.1
Bug,Documentation
v4.0.0Compare Source
Release Notes for 4.0.0
Release Notes for 4.0.0
laminas-servicemanager4.0.0 is here and finally enables projects to consumepsr/containerv2.0.0 after 2 years along with several type-additions and plugin manager decoupling.The migration guide is not written yet but will be at some point (once we added support for SM v4 to other components) later.
Added
ServiceManager#get,PluginManagerInterface#getandServiceLocatorInterface#buildnow explicitly implementmixedas return-type to synchronize types withContainerInterface#getpsr/containerv1.1 and v2.0ReflectionBasedAbstractFactoryvialaminas-cliRemoved
Laminas\ServiceManager\AbstractFactoryInterfaceLaminas\ServiceManager\FactoryInterfaceLaminas\ServiceManager\InitializerInterfaceLaminas\ServiceManager\DelegatorFactoryInterfacevendor/binare removed in favor of thelaminas-cliintegration. All CLI commands of v3.x are accessible viavendor/bin/laminas servicemanager:<v3.x command name>oncelaminas/laminas-cliis required in the projects dependenciesConfigInterfaceandConfig-class since these files did not provide any validation logic and were just used to proxy the configuration array structureAbstractPluginManager#validateandAbstractPluginManager::$instanceOfproperty as in v3.x, implementing plugin managers were able to implicitlyvalidatemixed. In case an implementing plugin manager is providing a single$instanceOfsuch aslaminas-cache, there is a new classAbstractSingleInstancePluginManageravailable which requires the$instanceOfproperty to be configuredBreaking Changes
AbstractPluginManagerdoes not extendServiceManageranymore and instead uses an ownServiceManagerinstance under the hood to manage plugin manager related services which can be configured the same way as in v3.xvendor/binare now integrated vialaminas-cliand can be called viavendor/bin/laminasoncelaminas/laminas-cliis part of the projects requirements. Read more about how to consume these commands here.AbstractPluginManagerdoes not provide thevalidate-Method anymore and requires migration action such as:AbstractSingleInstancePluginManagerin case the plugin manager only provides instances of a specific interface- or class-string (please be aware that the$instanceOfproperty now requires nativestringproperty type)validatemethod and verify whatever type has to be returned and/or just allowmixedas v3.x did when omitting$instanceOfpropertyConfigInterfaceandConfig-class since these files did not provide any validation logic and were just used to proxy the configuration array structureServiceManagernorAbstractPluginManagerdo validate the provided configuration at runtime anymore. due to the psalm-types provided toServiceManager#__construct,ServiceManager#configure,AbstractPluginManager#__constructandAbstractPluginManager#configure, the configuration schema is strictly typed and thus, a miss-configuration can be mitigated on static-analysis level prior actual runtimeAbstractPluginManager#getdoes not accept options anymore, in case an instance with options needs to be created,AbstractPluginManager#buildhas to be used4.0.0
Enhancement
$thistoselfthanks to @boesingReflectionBasedAbstractFactorymapped factories thanks to @boesingBC Break,Enhancement
psr/containerv2 thanks to @boesing and @danielspkServiceManager#getServiceLocatormethod thanks to @boesingServiceManagerinheritance forAbstractPluginManagerthanks to @boesingRFC
AbstractPluginManager#validatethanks to @boesingServiceManagerasfinaland changeAbstractPluginManagerto use composition over inheritance thanks to @boesingBC Break
container-interop/container-interoppolyfill thanks to @boesingrenovate
Bug
Configuration
📅 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 is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
Read more information about the use of Renovate Bot within Laminas.