olcs/olcs-laminas

This package is abandoned and no longer maintained. No replacement package was suggested.

There is no license information available for the latest version (3.0.3) of this package.

List of olcs laminas dependencies that are common across all repos

3.0.3 2023-09-14 12:52 UTC

Requires

• laminas/laminas-authentication: ^2.5
• laminas/laminas-cache: ^3
• laminas/laminas-cache-storage-adapter-redis: ^2
• laminas/laminas-code: ^4
• laminas/laminas-console: ^2.5
• laminas/laminas-crypt: ^3
• laminas/laminas-dependency-plugin: ^2
• laminas/laminas-escaper: ^2.5
• laminas/laminas-eventmanager: ^3
• laminas/laminas-filter: ^2.5
• laminas/laminas-form: ^3
• laminas/laminas-http: ^2.5
• laminas/laminas-i18n: ^2.5
• laminas/laminas-inputfilter: ^2.5
• laminas/laminas-json: ^3
• laminas/laminas-loader: ^2.5
• laminas/laminas-log: ^2.5
• laminas/laminas-mail: ^2.5
• laminas/laminas-math: ^3
• laminas/laminas-mime: ^2.5
• laminas/laminas-modulemanager: ^2.5
• laminas/laminas-mvc: ^3
• laminas/laminas-mvc-console: ^1.3
• laminas/laminas-mvc-i18n: ^1
• laminas/laminas-mvc-plugin-flashmessenger: ^1
• laminas/laminas-mvc-plugin-prg: ^1
• laminas/laminas-navigation: ^2.5
• laminas/laminas-router: ^3
• laminas/laminas-serializer: ^2.5
• laminas/laminas-servicemanager: ^3
• laminas/laminas-session: ^2.5
• laminas/laminas-stdlib: ^3
• laminas/laminas-text: ^2.5
• laminas/laminas-uri: ^2.5
• laminas/laminas-validator: ^2.5
• laminas/laminas-view: ^2.5
• laminas/laminas-xml: ^1
• lm-commons/lmc-rbac-mvc: ^3

Requires (Dev)

• elendev/composer-push: 1.0.3
• laminas/laminas-component-installer: ^3
• laminas/laminas-developer-tools: *
• san/san-session-toolbar: *

Unknown License

README

List of OLCS Laminas dependencies that are common across all repos

see https://dvsa.atlassian.net/browse/VOL-3206 for info on how and why this repo was created

versioning

Versions for this repo follow the approximate Laminas version we're targeting, so begin at 2.5.

These days, Laminas packages aren't all jumping version numbers at the same time, and indeed some are still on v2. So in practice, "version we're targeting" is likely to mean the service manager version, since that's where most upgrade blockers are found.

The idea is that we'll now be able to upgrade our backend, internal or selfserve nodes as soon as they're compatible, by swapping the version of this repo.

pushing tags to Nexus

As we'll be maintaining two sets of tags going forward (initially 2.5.x and 3.0.x) we won't be able to use the update dependency Jenkins job, or the 4.206.x naming. Instead check out the relevant tag from gitlab and run this from the command line:

composer push (tag name)