Your requirements could not be resolved to an installable set of packages.

[jpuck]

You're currently requiring a development branch of a package.

For others to use color-contrast-php in their projects, they must declare a dev minimum stability because composer defaults to stable, otherwise they'll get a dependency resolution conflict during installation.

Alternatively, you could try to convince @mikeemoo to make a release tag for ColorJizz-PHP and require that as a stable version. Or fork it, make your own release, and then require that version.

[davidgorges]

Thanks, there's already an open issue for version tagging in the ColorJizz lib. I prefer not to fork it, but you're right.

[jpuck]

In deed I upvoted your issue, but @mikeemoo doesn't appear to be very active on Github.

You've made a fabulous package and it's been working perfectly for me. I'm quite surprised this useful utility has gone relatively undiscovered thus far. Really makes WCAG compliance a cinch with dynamic color schemes, thanks!

[jpuck]

I don't know how I missed it, but it appears as though he added a 1.0.0 release tag back in November.

I commented on mikeemoo/ColorJizz-PHP#10 to point out that packagist hasn't picked up the tag.

I'll submit another PR with the vcs repository in composer.json that will allow faster resolution which will always see the available tags.

[davidgorges]

Thank you @jpuck for your help! Very much appreciated.

[jpuck]

@davidgorges no problem. would you mind making a new release tag (e.g. v0.1.1) to pick up the stable changes in packagist? thanks

[jpuck]

@davidgorges hey, not sure if you saw my last comment on this issue, but I would like to require your package as a dependency inside a project without declaring minimum stability as dev, but I need a new release tag from you to do so. thanks

[davidgorges]

@jpuck thanks for reminding me. Just created v.0.1.1