Rob
We could release a tagged version, sure. But there are still some PR's open and several feature requests. I don't really know which should be implemented before a 1.0 or...
You can `--ignore-platform-reqs`, if you insist on running a php version that is considered end-of-life.
You should be able to override the stability for a singe package explicitly by using the stability flags in the requirement (`@dev|@alpha|@beta`) or by require'ing a `dev-` branch. E.g. ```...
You're drifting off-topic though. This issue is about tagging a Satis release so people can lock in a "stable" version.
I mean, this issue/thread is about tagging Satis (currently there is just a master branch). This has nothing to do with the requirements that Satis has in its own composer.json....
How are you running satis in jenkins? Can you elaborate more on this?
Satis leverages Composer, and Composer does not support this currently afaik. > and tags on certain branches FYI: tags are not stored on branches. Tags are just objects by themselves....
Are you sure that is a solution? Because https://github.com/composer/composer/issues/7520 seems to suggest otherwise.
@Wirone there is no roadmap. Satis is almost entirely community maintained. I merely do some housekeeping from time to time. Versions can be tagged upon request. But I generally recommend...
Then go address it.