Skip to content

Fix interaction between dependencies:update and DEVELOPMENT_BUILD #1294

@josephsnyder

Description

@josephsnyder

Using the new dependencies:update command during the build of a DEVELOPMENT system leads to some undesirable interactions. The blind updating of

            "name": "symfony/options-resolver",
            "version": "v5.4.11",
<...>
            "require": {
                "php": ">=7.2.5",
                "symfony/deprecation-contracts": "^2.1|^3",
                "symfony/polyfill-php73": "~1.0",
                "symfony/polyfill-php80": "^1.16"
            },

from v5.4.11 to v6.2.5 (currently) removes the dependency on symfony/polyfill-php73.

            "name": "symfony/options-resolver",
            "version": "v6.2.5",
<...>
            "require": {
                "php": ">=8.1",
                "symfony/deprecation-contracts": "^2.1|^3"
            },
            "type"

This library though, is still looked for when executing the style test on the system:

https://open.cdash.org/test/958292463

Either better limit the versions marked as acceptable or stop using the update command during the generation of the docker images.

Metadata

Metadata

Assignees

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions