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 |
8698709 to
c53b814
Compare
Contributor
Author
|
c53b814 to
20f80a7
Compare
| datasource | package | from | to | | ---------- | ------------------------------ | ------ | ----- | | packagist | laminas/laminas-serializer | 2.17.0 | 3.0.0 | | packagist | laminas/laminas-servicemanager | 3.22.1 | 4.2.0 | Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
20f80a7 to
afe759d
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:
^2.14.0->^3.0.0^3.0.3->^3.0.3 || ^4.0.0Release Notes
laminas/laminas-serializer (laminas/laminas-serializer)
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 @boesinglaminas/laminas-servicemanager (laminas/laminas-servicemanager)
v4.2.0Compare Source
Release Notes for 4.2.0
Feature release (minor)
4.2.0
Enhancement
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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
Read more information about the use of Renovate Bot within Laminas.