You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
The text was updated successfully, but these errors were encountered:
Hi! 👋
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:
molecule-plugins/pyproject.toml
Line 43 in b48ead5
Can you please only do this in pre-release versions of this project and not in (stable) patch-level releases? 😸
When looking at 23.5.0, it is handled correctly there:
molecule-plugins/pyproject.toml
Line 42 in c516dac
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.
The text was updated successfully, but these errors were encountered: