laminas-feed Update Laminas packages (major)

Update Laminas packages (major)

Open renovate[bot] opened this issue 11 months ago • 2 comments

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
laminas/laminas-cache (source)	`^2.13.2 \|\| ^3.12` -> `^4.0`
laminas/laminas-cache-storage-adapter-memory	`^1.1.0 \|\| ^2.3` -> `^3.0`
laminas/laminas-coding-standard (source)	`~2.5.0` -> `~3.0.0`
laminas/laminas-servicemanager (source)	`^3.22.1` -> `^4.0.0`
laminas/laminas-validator (source)	`^2.46` -> `^3.0`

Release Notes

laminas/laminas-cache (laminas/laminas-cache)

`v4.0.4`

Compare Source

Release Notes for 4.0.4

4.0.4

Total issues resolved: 0
Total pull requests resolved: 3
Total contributors: 1

Documentation

328: Add new max&#95;items Memory adapter option thanks to @boesing
327: Add new FilesystemOptions related to Filesystem v3.0 thanks to @boesing
326: Update documentation to reflect most recent changes regarding v4 and adapters thanks to @boesing

`v4.0.3`

Compare Source

Release Notes for 4.0.3

4.0.3

Total issues resolved: 0
Total pull requests resolved: 1
Total contributors: 1

Bug

322: Add adapter options template to StorageInterface usage thanks to @boesing

`v4.0.2`

Compare Source

Release Notes for 4.0.2

4.0.x bugfix release (patch)

4.0.2

Total issues resolved: 0
Total pull requests resolved: 1
Total contributors: 1

Bug

321: Add adapter options template to StorageInterface usage thanks to @boesing

`v4.0.1`

Compare Source

Release Notes for 4.0.1

4.0.x bugfix release (patch)

4.0.1

Total issues resolved: 0
Total pull requests resolved: 1
Total contributors: 1

Bug

319: Add missing template param for StorageInterface thanks to @boesing

laminas-cache 4.0.0 is here and finally adds native types everywhere, adds support for psr/cache and psr/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

Every adapter which supports metadata now implements MetadataCapableInterface and provides a dedicated object containing all the metadata values it supports
Adds support for psr/cache and psr/simple-cache v2 & v3

Removed

supportedMetadata capability from Capabilities
KeyListIterator::CURRENT_AS_METADATA mode along with Laminas\Cache\Exception\MissingKeyException
automatic instantiation of SerializerInterface when calling PluginOptions#getSerializer
Increment and decrement feature from StorageInterface, so there is no more StorageInterface#incrementItem, StorageInterface#decrementItem, StorageInterface#decrementItems and StorageInterface#incrementItems
- this also removes incrementItem, incrementItems, decrementItem, derementItems events (pre, post and exception)
dependency inversion on virtual package laminas/laminas-cache-storage-adapter-implementation which now allows laminas-cache to be required without a concrete storage adapter implementation
removed support for psr/cache and psr/simple-cache v1

Breaking Changes

AbstractAdapter and StorageInterface are not aware of the methods getMetadata anymore. These were moved to the new MetadataCapableInterface
Capabilities do not provide supportedMetadata 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 anyway
KeyListIterator and the corresponding IteratorInterface does not provide the mode CURRENT_AS_METADATA anymore
PluginOptions#getSerializer does not create a serializer anymore if a string option was passed, instead, the string is returned
Increment and decrement feature was removed from StorageInterface, so there is no more StorageInterface#incrementItem, StorageInterface#decrementItem, StorageInterface#decrementItems and StorageInterface#incrementItems
- this also removes incrementItem, incrementItems, decrementItem, derementItems events (pre, post and exception)
Every method now has native return types
Every property now has native types
Every method argument now has native types
ObjectCache does not inherit the CallbackCache pattern anymore

4.0.0

Total issues resolved: 9
Total pull requests resolved: 18
Total contributors: 4

Release Notes for 3.12.2

3.12.x bugfix release (patch)

3.12.2

Total issues resolved: 1
Total pull requests resolved: 1
Total contributors: 1

Documentation

300: Documentation: Add ssl&#95;context option to RedisCluster documentation thanks to @boesing

`v3.12.1`

Compare Source

Release Notes for 3.12.1

3.12.x bugfix release (patch)

3.12.1

Total issues resolved: 1
Total pull requests resolved: 1
Total contributors: 1

Bug

286: Infinite loop when fetching some cache-related services via container in projects without registered config service thanks to @InvisibleSmiley

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 for psr/cache and psr/simple-cache v2 & v3, supports laminas/laminas-cache v4 and introduces an all new metadata and internal persistence logic.

The Memory adapter had its flaws by juggling with the memory_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 introducing max_items which limits the amount of items persisted to the Memory adapter (defaults to unlimited). Once the max_items are exceeding, the adapter automatically removes the oldest entries to make room for new items.

Added

Dedicated Metadata object for Memory#getMetadata
Adds support for psr/cache and psr/simple-cache v2 & v3
Memory now allows passing a ClockInterface via its constructor
MemoryOptions now has max_items configuration to limit the amount of items to be cached. When the limit exceeds, the adapter automatically drops older items

Changed

Memory adapter now supports per-item TTL and thus, the TTL is calculated on-write rather than on-read
Memory adapter now supports max_items option which can be used to limit the amount of items persisted to the cache

Removed

MemoryOptions#setMemoryLimit , there is no replacement. It is recommended to use the max_items option instead
MemoryOptions#getMemoryLimit, there is no relacement

3.0.0

Total issues resolved: 2
Total pull requests resolved: 4
Total contributors: 2

renovate

64: Update dependency laminas/laminas-cache-storage-adapter-test to v4 thanks to @renovate[bot]

RFC

63: [RFC]: Serialize objects thanks to @boesing

Enhancement

61: Bump storage implementation version thanks to @boesing

BC Break,Bug,Enhancement

60: Replace memory&#95;limit with max&#95;items thanks to @boesing

BC Break,Bug

58: Add support for laminas/laminas-cache v4 thanks to @boesing

laminas/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

Total issues resolved: 0
Total pull requests resolved: 2
Total contributors: 1

Documentation,Enhancement

86: docs: Add missing docs for v3 thanks to @michalbundyra
85: chore: Update links from squizlabs to PHPCSStandards thanks to @michalbundyra

`v3.0.0`

Compare Source

Release Notes for 3.0.0

Backwards incompatible release (major)

3.0.0

Total issues resolved: 0
Total pull requests resolved: 3
Total contributors: 2

renovate

84: Lock file maintenance thanks to @renovate[bot]

Enhancement

83: feat: upgrade to slevomat/coding-standard ^8 thanks to @alexraputa

BC Break,renovate

75: chore(deps): update dependency slevomat/coding-standard to v8 - abandoned thanks to @renovate[bot]

laminas/laminas-servicemanager (laminas/laminas-servicemanager)

`v4.2.0`

Compare Source

Release Notes for 4.2.0

Feature release (minor)

4.2.0

Total issues resolved: 0
Total pull requests resolved: 1
Total contributors: 1

Enhancement

237: Allow varexporter v0.5 thanks to @snapshotpl

`v4.1.0`

Compare Source

Release Notes for 4.1.0

Feature release (minor)

4.1.0

Total issues resolved: 1
Total pull requests resolved: 3
Total contributors: 2

Documentation

234: Merge release 4.0.2 into 4.1.x thanks to @github-actions[bot]
232: Merge release 4.0.1 into 4.1.x thanks to @github-actions[bot]

Documentation,Enhancement

230: Make ServiceLocatorInterface#get() generic thanks to @InvisibleSmiley

`v4.0.2`

Compare Source

Release Notes for 4.0.2

4.0.x bugfix release (patch)

4.0.2

Total issues resolved: 0
Total pull requests resolved: 1
Total contributors: 1

Bug,Documentation

233: Update docs-build workflow triggers and environment variables thanks to @froschdesign

`v4.0.1`

Compare Source

Release Notes for 4.0.1

4.0.x bugfix release (patch)

4.0.1

Total issues resolved: 0
Total pull requests resolved: 1
Total contributors: 1

Bug,Documentation

226: Fixes documentation to support different versions thanks to @froschdesign

`v4.0.0`

Compare Source

Release Notes for 4.0.0

laminas-servicemanager 4.0.0 is here and finally enables projects to consume psr/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

Several native type-additions including property-, argument- and return-types and a lot more psalm types
ServiceManager#get, PluginManagerInterface#get and ServiceLocatorInterface#build now explicitly implement mixed as return-type to synchronize types with ContainerInterface#get
Support for psr/container v1.1 and v2.0
Ahead of Time factory creation for services explicitly using ReflectionBasedAbstractFactory via laminas-cli

Removed

Dropped support for PHP <8.1
Removed deprecated interfaces such as
- Laminas\ServiceManager\AbstractFactoryInterface
- Laminas\ServiceManager\FactoryInterface
- Laminas\ServiceManager\InitializerInterface
- Laminas\ServiceManager\DelegatorFactoryInterface
CLI commands which were exposed via vendor/bin are removed in favor of the laminas-cli integration. All CLI commands of v3.x are accessible via vendor/bin/laminas servicemanager:<v3.x command name> once laminas/laminas-cli is required in the projects dependencies
Removed deprecated ConfigInterface and Config-class since these files did not provide any validation logic and were just used to proxy the configuration array structure
Removed AbstractPluginManager#validate and AbstractPluginManager::$instanceOf property as in v3.x, implementing plugin managers were able to implicitly validate mixed. In case an implementing plugin manager is providing a single $instanceOf such as laminas-cache, there is a new class AbstractSingleInstancePluginManager available which requires the $instanceOf property to be configured

Breaking Changes

AbstractPluginManager does not extend ServiceManager anymore and instead uses an own ServiceManager instance under the hood to manage plugin manager related services which can be configured the same way as in v3.x
Dedicated CLI commands which were previously linked to vendor/bin are now integrated via laminas-cli and can be called via vendor/bin/laminas once laminas/laminas-cli is part of the projects requirements. Read more about how to consume these commands here.
AbstractPluginManager does not provide the validate-Method anymore and requires migration action such as:
- extend 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 native string property type)
- implement validate method and verify whatever type has to be returned and/or just allow mixed as v3.x did when omitting $instanceOf property
Removed deprecated ConfigInterface and Config-class since these files did not provide any validation logic and were just used to proxy the configuration array structure
neither ServiceManager nor AbstractPluginManager do validate the provided configuration at runtime anymore. due to the psalm-types provided to ServiceManager#__construct, ServiceManager#configure, AbstractPluginManager#__construct and AbstractPluginManager#configure, the configuration schema is strictly typed and thus, a miss-configuration can be mitigated on static-analysis level prior actual runtime
AbstractPluginManager#get does not accept options anymore, in case an instance with options needs to be created, AbstractPluginManager#build has to be used