Feature description
Please add an opt-in flag (like --include-experimental or -x) to list-versions and list-patches to include experimental versions in the CLI output.
Currently, both commands only show stable versions. If you intentionally want to target an experimental app version, you have to manually parse the .mpp or patches-list.json files.
Motivation
This is mainly for automated build pipelines and power users.
If a script runs list-versions to find the highest supported app version to download, it simply cannot see the experimental ones because the CLI doesn't print them. Because of this, the script doesn't even know that newer app versions are already supported.
Adding an opt-in flag would solve this, allowing scripts to see and target the absolute latest versions. Since it's optional, the default behavior stays exactly the same and won't break anyone's existing workflows.
Acknowledgements
Feature description
Please add an opt-in flag (like
--include-experimentalor-x) tolist-versionsandlist-patchesto include experimental versions in the CLI output.Currently, both commands only show stable versions. If you intentionally want to target an experimental app version, you have to manually parse the
.mpporpatches-list.jsonfiles.Motivation
This is mainly for automated build pipelines and power users.
If a script runs
list-versionsto find the highest supported app version to download, it simply cannot see the experimental ones because the CLI doesn't print them. Because of this, the script doesn't even know that newer app versions are already supported.Adding an opt-in flag would solve this, allowing scripts to see and target the absolute latest versions. Since it's optional, the default behavior stays exactly the same and won't break anyone's existing workflows.
Acknowledgements