-
-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Laminas packages (major) #64
base: 2.20.x
Are you sure you want to change the base?
Conversation
⚠ 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
|
f2cd103
to
b0f4671
Compare
b0f4671
to
405a560
Compare
|
405a560
to
7e5043d
Compare
3a8ce05
to
8210e0d
Compare
8210e0d
to
09d2c6c
Compare
09d2c6c
to
f9b94b0
Compare
6db219c
to
d2f2626
Compare
d2f2626
to
c557c8d
Compare
bd7382a
to
15c12fa
Compare
15c12fa
to
8599d79
Compare
2901bc1
to
f92dd2d
Compare
c6fb250
to
486fa3e
Compare
486fa3e
to
d5ee704
Compare
a02f220
to
bbd9488
Compare
c9afcc7
to
7a24429
Compare
68b0a45
to
2f7165e
Compare
| datasource | package | from | to | | ---------- | -------------------------------------------- | ------ | ----- | | packagist | laminas/laminas-cache | 3.12.2 | 4.1.0 | | packagist | laminas/laminas-cache-storage-adapter-memory | 2.3.0 | 3.1.0 | | packagist | laminas/laminas-coding-standard | 2.5.0 | 3.0.1 | | packagist | laminas/laminas-servicemanager | 3.23.0 | 4.3.0 | Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
2f7165e
to
aec7881
Compare
This PR contains the following updates:
^3.12.2
->^4.0.0
^2.3.0
->^3.0.0
^2.5.0
->^3.0.0
^3.22.1
->^4.0.0
Release Notes
laminas/laminas-cache (laminas/laminas-cache)
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-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 @boesinglaminas/laminas-coding-standard (laminas/laminas-coding-standard)
v3.0.1
Compare Source
Release Notes for 3.0.1
3.0.x bugfix release (patch)
3.0.1
Documentation,Enhancement
v3.0.0
Compare Source
Release Notes for 3.0.0
Backwards incompatible release (major)
3.0.0
renovate
Enhancement
slevomat/coding-standard
^8 thanks to @alexraputaBC Break,renovate
laminas/laminas-servicemanager (laminas/laminas-servicemanager)
v4.3.0
Compare Source
Release Notes for 4.3.0
Feature release (minor)
Introduces PHP 8.4 Support
4.3.0
Enhancement
Documentation,Enhancement
renovate
v4.2.1
Compare Source
Release Notes for 4.2.1
4.2.x bugfix release (patch)
4.2.1
Documentation,Enhancement
v4.2.0
Compare Source
Release Notes for 4.2.0
Feature release (minor)
4.2.0
Enhancement
v4.1.0
Compare Source
Release Notes for 4.1.0
Feature release (minor)
4.1.0
Documentation
Documentation,Enhancement
ServiceLocatorInterface#get()
generic thanks to @InvisibleSmileyv4.0.2
Compare Source
Release Notes for 4.0.2
4.0.x bugfix release (patch)
4.0.2
Bug,Documentation
v4.0.1
Compare Source
Release Notes for 4.0.1
4.0.x bugfix release (patch)
4.0.1
Bug,Documentation
v4.0.0
Compare Source
Release Notes for 4.0.0
Release Notes for 4.0.0
laminas-servicemanager
4.0.0 is here and finally enables projects to consumepsr/container
v2.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#get
andServiceLocatorInterface#build
now explicitly implementmixed
as return-type to synchronize types withContainerInterface#get
psr/container
v1.1 and v2.0ReflectionBasedAbstractFactory
vialaminas-cli
Removed
Laminas\ServiceManager\AbstractFactoryInterface
Laminas\ServiceManager\FactoryInterface
Laminas\ServiceManager\InitializerInterface
Laminas\ServiceManager\DelegatorFactoryInterface
vendor/bin
are removed in favor of thelaminas-cli
integration. All CLI commands of v3.x are accessible viavendor/bin/laminas servicemanager:<v3.x command name>
oncelaminas/laminas-cli
is required in the projects dependenciesConfigInterface
andConfig
-class since these files did not provide any validation logic and were just used to proxy the configuration array structureAbstractPluginManager#validate
andAbstractPluginManager::$instanceOf
property as in v3.x, implementing plugin managers were able to implicitlyvalidate
mixed
. In case an implementing plugin manager is providing a single$instanceOf
such aslaminas-cache
, there is a new classAbstractSingleInstancePluginManager
available which requires the$instanceOf
property to be configuredBreaking Changes
AbstractPluginManager
does not extendServiceManager
anymore and instead uses an ownServiceManager
instance under the hood to manage plugin manager related services which can be configured the same way as in v3.xvendor/bin
are now integrated vialaminas-cli
and can be called viavendor/bin/laminas
oncelaminas/laminas-cli
is part of the projects requirements. Read more about how to consume these commands here.AbstractPluginManager
does not provide thevalidate
-Method anymore and requires migration action such as:AbstractSingleInstancePluginManager
in case the plugin manager only provides instances of a specific interface- or class-string (please be aware that the$instanceOf
property now requires nativestring
property type)validate
method and verify whatever type has to be returned and/or just allowmixed
as v3.x did when omitting$instanceOf
propertyConfigInterface
andConfig
-class since these files did not provide any validation logic and were just used to proxy the configuration array structureServiceManager
norAbstractPluginManager
do validate the provided configuration at runtime anymore. due to the psalm-types provided toServiceManager#__construct
,ServiceManager#configure
,AbstractPluginManager#__construct
andAbstractPluginManager#configure
, the configuration schema is strictly typed and thus, a miss-configuration can be mitigated on static-analysis level prior actual runtimeAbstractPluginManager#get
does not accept options anymore, in case an instance with options needs to be created,AbstractPluginManager#build
has to be used4.0.0
Enhancement
$this
toself
thanks to @boesingReflectionBasedAbstractFactory
mapped factories thanks to @boesingBC Break,Enhancement
psr/container
v2 thanks to @boesing and @danielspkServiceManager#getServiceLocator
method thanks to @boesingServiceManager
inheritance forAbstractPluginManager
thanks to @boesingRFC
AbstractPluginManager#validate
thanks to @boesingServiceManager
asfinal
and changeAbstractPluginManager
to use composition over inheritance thanks to @boesingBC Break
container-interop/container-interop
polyfill 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.