[BUG] users running pip install for Python 3.13 get 0.1.10

[dzsquared]

Bug Description

Since 2 very early versions of the Fabric CLI on pypi don't limit the Python version to < 3.13, users with either of the latest 2 versions (3.13 and 3.14) are accidentally installing old versions.

fabric-cli version

0.1.10

Python version

Python 3.13.7

Operating System

macOS

CLI Mode

Interactive mode

Authentication Method

Interactive browser login

Steps to Reproduce

1. Install Python on your machine, not reading documentation for any/all of the tools you use like Fabric CLI that have max version restrictions
2. Accidentally install Python 3.13 or 3.14 instead of 3.12
3. pip install ms-fabric-cli

Expected Behavior

Some combination of:

• no versions still published are installable with 3.13 and 3.14 (remove the 0.1.9 and 0.1.10 versions)
• add 3.13 since msal added 3.13 in September with 1.34.0

Actual Behavior

pip install ms-fabric-cli

results in 0.1.10 being installed

Additional Context

• Request to Declare Python 3.13 Compatibility on PyPI AzureAD/microsoft-authentication-library-for-python#850
• [Feature Request] Python 3.13 compatability AzureAD/microsoft-authentication-library-for-python#848
• MSAL Python 1.33.0b1 release AzureAD/microsoft-authentication-library-for-python#827

Possible Solution

No response

[ayeshurun]

Hi @dzsquared, thanks for raising this!

This is expected behavior for pip when installing packages on a system with a specific Python version. When you run pip install ms-fabric-cli (or any other library), pip uses the Python version it is associated with (in your case, Python 3.13) to determine which distribution or "wheel" of the package to download and install. It looks for the latest version of the package on PyPI that declares compatibility with Python 3.13 (and your operating system, macOS).

Please also be advised that since version 0.2.0, support for Python 3.13 and later has been discontinued due to incompatibilities with upstream dependencies requirements. This change was introduced to preserve project stability and ensure continued compatibility with our core dependency stack.

We appreciate your engagement and contribution to the project. This issue will be closed as not a bug.

[dzsquared]

I'm confused - did you want me to file this as a feature request now so that it can be tracked on the open source repo?

Maybe the bug is resolved by removing the 2 older released from pypi that don't block on version at all so at least customers don't get a very old version of Fabric CLI without noticing, and the feature request is to finish bumping dependencies.