Tagged Version 4 Requires Dev Dependency

[programster]

I'm just getting started with trying to use the tool, and if I perform:

composer require "corneltek/cliframework"

Then I get the following error message:

Text below just in case helps with SEO etc.

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

  Problem 1
    - corneltek/cliframework[4.1.0, ..., 4.1.2] require universal/universal 2.0.x-dev -> found universal/universal[dev-master, 2.0.x-dev (alias of dev-master)] but it does not match your minimum-stability.
    - Root composer.json requires corneltek/cliframework ^4.1 -> satisfiable by corneltek/cliframework[4.1.0, 4.1.1, 4.1.2].

You can also try re-running composer require with an explicit version constraint, e.g. "composer require corneltek/cliframework:*" to figure out if any version is installable, or "composer require corneltek/cliframework:^2.1" if you know which you need.

Installation failed, reverting ./composer.json to its original content.

I tried all of the 4.x versions, and all of them had the same issue where they are wanting to use the dev line of the Khttps://packagist.org/packages/universal/universal package. In the end I manually specified to use version 3 of the package to get this to work:

composer require "corneltek/cliframework:3"

It appears that you (c9s) are the maintainer of both. Can you not specify a tagged, stable versoin of the universal/universal package for the CLIFramework package to use? Don't forget that you can do something like 3.1.* on your dependency, so that the CLI framework can use the latest version that doesn't break signatures (if using some sort of semantic versioning).