Please do not depend on pre-release versions in stable releases

Hi! :wave:

I'm packaging this project for Arch Linux. Upon trying to upgrade to 23.5.3, I noticed that this project now depends on a pre-release version of molecule:

https://github.com/ansible-community/molecule-plugins/blob/b48ead5d12d80eb90ead14f1958d0e9ef79b8752/pyproject.toml#L43

Can you *please* only do this in pre-release versions of this project and not in (stable) patch-level releases? :smile_cat:

When looking at 23.5.0, it is handled correctly there:

https://github.com/ansible-community/molecule-plugins/blob/c516daca85ec477758de5aafdf5dc00307a3ebd4/pyproject.toml#L42

If I had bumped this version we would most likely yet again have a broken molecule + plugins on Arch Linux. Checking for these scenarios manually, instead of being able to rely on common practices (e.g. semver guarantees) is *very* time consuming and downstream packagers work on packaging this project in their free time.

This situation can be prevented by doing pre-releases (which we purposefully ignore downstream) for this project in which you rely on whatever pre-release version of your dependencies you require. Doing this in stable releases however is a recipe for disaster.

Review pyproject.toml around the dependency entry linked for version 23.5.3 and compare it with the 23.5.0 reference. Confirm that stable patch releases do not depend on pre-release molecule versions, while the project’s pre-release versions may use them. Done means the stable-release dependency declaration follows that policy.

Written by the indexing model from the issue text.