Does a dev-trunk shopware/core constraint allow Shopware 6.7.0.0?

A dev-trunk shopware/core declaration cannot be evaluated against Shopware 6.7.0.0.

A branch or alias constraint names something composer resolves at install time from a source this evaluator cannot see.

The bound this idiom derives

No single upper bound follows from the dev-trunk idiom alone.

dev-trunk derives no single bound, so whether it reaches Shopware 6.7.0.0 is decided clause by clause rather than by one cut-off.

The next release up

The next release line above Shopware 6.7.0.0 is 6.7.1.

Whether a dev-trunk declaration reaches Shopware 6.7.1 cannot be evaluated from the declaration alone.

The same declaration against every version we evaluate

TargetVerdictStatement
Shopware 6.6.10.3unevaluableA dev-trunk shopware/core declaration cannot be evaluated against Shopware 6.6.10.3.
Shopware 6.7.0.0unevaluableA dev-trunk shopware/core declaration cannot be evaluated against Shopware 6.7.0.0.

Neighbouring declarations at Shopware 6.7.0.0

DeclarationFamilyAt this target Upper boundWhy
^6.4caretA ^6.4 shopware/core declaration allows Shopware 6.7.0.0.The ^6.4 idiom stops below version 7.Shopware 6.7.0.0 sits below the bound ^6.4 derives, which is why the declaration reaches it.
~6.4.0tildeA ~6.4.0 shopware/core declaration excludes Shopware 6.7.0.0.The ~6.4.0 idiom stops below version 6.5.Shopware 6.7.0.0 sits at or above the bound ~6.4.0 derives, which is why the declaration stops short of it.
6.6.*wildcardA 6.6.* shopware/core declaration excludes Shopware 6.7.0.0.No single upper bound follows from the 6.6.* idiom alone.6.6.* derives no single bound, so whether it reaches Shopware 6.7.0.0 is decided clause by clause rather than by one cut-off.

What this tells you, and what it does not

Check a real shop

Run your composer.lock through the checker — it reads declarations the same way this page does, across every plugin at once.

Neighbouring pages