Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Preview versions in index.json is not valid semantic versions #7875

Open
o-l-a-v opened this issue Aug 10, 2024 · 2 comments
Open

Preview versions in index.json is not valid semantic versions #7875

o-l-a-v opened this issue Aug 10, 2024 · 2 comments
Assignees
Labels
Azure CLI Team The command of the issue is owned by Azure CLI team customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Milestone

Comments

@o-l-a-v
Copy link

o-l-a-v commented Aug 10, 2024

Describe the bug

Preview version numbers in index.json, fetched with az extension list-available, is not valid semantic versions.

Example:

PS > az extension list-available | ConvertFrom-Json | Select-Object -Last 1

experimental : False
installed    : False
name         : workloads
preview      : True
summary      : Microsoft Azure Command-Line Tools Workloads Extension.
version      : 1.1.0b2

PS >

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

PS > [semver]'1.1.0b2'

InvalidArgument: Cannot convert value "1.1.0b2" to type "System.Management.Automation.SemanticVersion". Error: "The input string '' was not in a correct format."

PS >

Issue script & Debug output

Not relevant.

Expected behavior

Use standard version schemes.

Environment Summary

Not relevant.

Additional context

No response

@o-l-a-v o-l-a-v added the bug This issue requires a change to an existing behavior in the product in order to be resolved. label Aug 10, 2024
@yonzhan
Copy link
Collaborator

yonzhan commented Aug 10, 2024

Thank you for opening this issue, we will look into it.

@microsoft-github-policy-service microsoft-github-policy-service bot added question The issue doesn't require a change to the product in order to be resolved. Most issues start as that customer-reported Issues that are reported by GitHub users external to the Azure organization. labels Aug 10, 2024
@o-l-a-v
Copy link
Author

o-l-a-v commented Aug 10, 2024

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.

@yonzhan yonzhan added Azure CLI Team The command of the issue is owned by Azure CLI team and removed bug This issue requires a change to an existing behavior in the product in order to be resolved. labels Aug 10, 2024
@yonzhan yonzhan added this to the Backlog milestone Aug 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Azure CLI Team The command of the issue is owned by Azure CLI team customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Projects
None yet
Development

No branches or pull requests

3 participants