Can't install azure-cli because of pinned beta versions

Describe the bug

I'm trying to use
uv tool install azure-cli@latest
but installs version 2.0.67.

After some investigation it turns out that this due to lots of pre-release packages being added since then.
Could you clean up your dependencies in https://github.com/Azure/azure-cli/blob/dev/src/azure-cli/setup.py to use stable versions?

This is the problematic packages I found:

azure-batch==15.0.0b1
azure-keyvault-securitydomain==1.0.0b1
azure-mgmt-authorization==5.0.0b1
azure-mgmt-batchai==7.0.0b1
azure-mgmt-botservice~=2.0.0b3
azure-mgmt-containerinstance==10.2.0b1
azure-mgmt-containerregistry==14.1.0b1
azure-mgmt-datalake-store~=1.1.0b1
azure-mgmt-eventgrid==10.2.0b2
azure-mgmt-eventhub~=12.0.0b1
azure-mgmt-extendedlocation==1.0.0b2
azure-mgmt-hdinsight==9.1.0b2
azure-mgmt-iotcentral~=10.0.0b1
azure-mgmt-iothub==5.0.0b1
azure-mgmt-loganalytics==13.0.0b4
azure-mgmt-monitor~=7.0.0b1
azure-mgmt-policyinsights==1.1.0b4
azure-mgmt-postgresqlflexibleservers==1.1.0b2
azure-mgmt-rdbms==10.2.0b17
azure-mgmt-mysqlflexibleservers==1.0.0b3
azure-mgmt-resource-deployments==1.0.0b1
azure-mgmt-resource-deploymentscripts==1.0.0b1
azure-mgmt-resource-deploymentstacks==1.0.0b1
azure-mgmt-resource-templatespecs==1.0.0b1
azure-mgmt-servicebus~=10.0.0b1
azure-mgmt-servicefabricmanagedclusters==2.1.0b1
azure-mgmt-servicelinker==1.2.0b3
azure-mgmt-signalr==2.0.0b2
azure-mgmt-sqlvirtualmachine==1.0.0b5
azure-mgmt-sql==4.0.0b22
azure-mgmt-synapse==2.1.0b5

to anyone comming here looking for a quick solution:
uv tool install --prerelease=allow azure-cli@latest
will get you the latest version.

Related command

uv tool install azure-cli@latest

Errors

• azure-cli==2.0.67
  ...
  warning: The package urllib3==2.5.0 does not have an extra named secure

Issue script & Debug output

N/A

Expected behavior

Expect it to install latest version. It would then look like this:
+ azure-cli==2.79.0

Environment Summary

Not sure if this is relevant in this context, but here it is:

azure-cli 2.57.0 *

core 2.57.0 *
telemetry 1.1.0

Dependencies:
msal 1.26.0
azure-mgmt-resource 23.1.0b2

Python location 'C:\Program Files\Microsoft SDKs\Azure\CLI2\python.exe'
Extensions directory 'C:\Users\redacted.azure\cliextensions'

Python (Windows) 3.11.7 (tags/v3.11.7:fa7a6f2, Dec 4 2023, 19:24:49) [MSC v.1937 64 bit (AMD64)]

Legal docs and information: aka.ms/AzureCliLegal

Additional context

From astral-sh/uv#14415 (comment) :

• Revert "Use setuptools entry_points for az executable" #1042
• Support python3 executable when running az #1043
• az wrongly assumes Python executable #7367
• No module named azure in pyvenv #3989
• convert az bash script into console entry point #8208
• Rewrite az in python #10516

[yonzhan]

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

[bebound]

Thanks for raising this.
Unfortunately, some modules rely on the pre-release azure-xx packages, which is not under our control.

I would expect that Azure is in control of azure-cli and all its Azure dependencies?

[bebound]

https://github.com/Azure/azure-sdk-for-python determines the version of azure-xx, and using which SDK is controlled by service team.

Are you saying that these aren't real dependencies for the package or that the issue needs to be raised somewhere else?

This one for examples has been deprecated since 2022: https://github.com/Azure/azure-sdk-for-python/blob/main/sdk/app/azure-mgmt-app/CHANGELOG.md

[asmaier]

I think it is not honest to claim in setup.py

CLASSIFIERS = [
    'Development Status :: 5 - Production/Stable',

and then depend on so many beta versions. Please fix this.

P.S. A workaround is

uv add azure-cli --prerelease=allow

But to run your scripts you need to either set --prerelease=allow also for uv run or you do

uv run --no-sync <your-script.py>