Dependency Conflict Issue about tombstone HOT 3 CLOSED

First, let me clear this is not a bug, it's standard behavior by the package manager. If you do a composer require scheb/tombstone you say "give me any scheb/tombstone version that you can find to be working within my existing version constraints". There is no guarantee to get the latest version. If you want the latest version, you have to tell Composer the version constraint that you want.

The reason why you get v0.8.0 of the package is phpunit/php-text-template: ^1.2.1|^2.0 being declared as a dependency. If you have PHPUnit already installed with a newer version of phpunit/php-text-template, then the package manager will look for a version that is compatible with this requirement. And that's likely going to be one of the older versions, which do not have a dependency on phpunit/php-text-template at all.

The way out of this misery is likely to bump up the version constraints on the package dependencies to newer package versions. But I have my doubts that supporting a version range from PHP7.1-compatible to PHP8.3-compatible dependencies is going to work. Likely would need to ditch PHP7 and release a new major version that supports the range of PHP8 versions.

from tombstone.

this explains why it was slightly painful getting this to work initially 😅

from tombstone.

I’ve not had a chance to looking into the differences between different versions and if it can just be added (I doubt it)

but ill like to try!

I think there is value in keeping as many versions of PHP supported as possible as just because a project is on the latest version doesn’t mean it’s well maintained or free of dead code.

If it’s not possible at least documenting the behavior so people are aware.

What are your thoughts?

from tombstone.