Open o-l-a-v opened 1 month ago
Thank you for opening this issue, we will look into it.
So Python has its own version scheme?
Dotnet has NuGet.Versioning which also isn't semver compatible, so maybe I can't complain.
Would still be great with a semver compatible version number in the metadata somewhere.
Describe the bug
Preview version numbers in
index.json
, fetched withaz extension list-available
, is not valid semantic versions.Example:
If one ads a hyphen to it
1.1.0b2
=>1.1.0-b2
, it becomes valid.Why use a non-standard version scheme? Makes it harder to parse.
Related command
az extension list-available
Errors
Issue script & Debug output
Not relevant.
Expected behavior
Use standard version schemes.
Environment Summary
Not relevant.
Additional context
No response