[FEATURE] Update CLI to support more modern python versions

[JoelMiller74]

Use Case / Problem

Problem:
I recently had a specific use for Fabric CLI. I keep it up to date and know that I recently updated it. However, I ran the update again and it said it was already up to date. I started working away but it became more and more apparent that none of the documentation matched what I was seeing. After wasting several hours, I finally determined that even though I was on the latest version available , I was only on version 0.1.10! I tried updating again, uninstalling, clearing the cache, reinstalling with --no-cache-dir. I ran pip index versions ms-fabric-cli and it also confirmed that the newest version available was 0.1.10. Finally, after running pip install git+https://github.com/microsoft/fabric-cli.git@v1.2.0 I received a worthy error: ERROR: Package 'ms-fabric-cli' requires a different Python: 3.13.9 not in '<3.13,>=3.10'.
I had Python 3.13.9 installed because I needed it for some work in VSCode that I was doing. Fabric CLI required 3.10 to 3.12. Although, if I had a newer version installed, it would gladly install Fabric CLI version 0.1.10.
To work around this issue, I installed Python 3.12, created and activated an environment, and installed Fabric CLI 1.2.0 without an issue.
The next day, I opened the Microsoft Fabric Subreddit and someone else described the exact same issue as me.
Microsoft Fabric Subreddit - ms-fabric-cli version

Proposed Solution

Options to resolve (short-term, medium-term, and long-term)

1. Update the documentation to call this issue out better and how to handle it.
2. Make a patch update that will identify the issue above and not just install a very old version of Fabric CLI without notification, but provide a fatal error that the required Python version is not installed. Please do not just add a comment and install the old version. This is a CLI and I expect to install, update, and use this CLI in a very automated manner. I am OK with the update failing because of a missing pre-requisite, but I am not OK with an install of the CLI succeeding with a very old version and not letting anyone know.
3. Add support for 3.13 and 3.14.

• 3.14 is current LTS and used often.
• 3.12 is stable and mature, but is not in active support.

Alternatives Considered

No response

Impact Assessment

• This would help me personally
• This would help my team/organization
• This would help the broader fabric-cli community
• This aligns with Microsoft Fabric roadmap items

Implementation Attestation

• I understand this feature should maintain backward compatibility with existing commands
• I confirm this feature request does not introduce performance regressions for existing workflows
• I acknowledge that new features must follow fabric-cli's established patterns and conventions

Implementation Notes

No response

[HasanAboShally]

Thanks for the detailed report, @JoelMiller74 — you hit a real sharp edge.

What’s happening (and why you ended up on 0.1.10)

• Newer ms-fabric-cli releases currently declare a Python requirement of >=3.10,<3.13. So on Python 3.13, those releases are considered incompatible by the installer.
• pip does not necessarily fail just because the latest release is incompatible. It will try to find the newest release that is compatible with your interpreter and may install that instead. If an older release (like 0.1.10) still supports your Python, you can end up with a much older CLI without an obvious warning.
• That resolver behavior is driven by pip; the package can’t force pip to error in cases where an older compatible version exists.

Why we currently gate Python 3.13 (and why auth deps matter)

• Fabric CLI depends on Microsoft identity libraries (including msal[broker] and msal_extensions) for interactive auth/broker flows and secure token caching.
• Before widening Python support, we validate the full dependency chain and our test matrix on the new interpreter version—especially around authentication and caching behavior—so we don’t ship a “supported” version that breaks login flows.

Python 3.13 support

Good news: we’re working on adding Python 3.13 support soon. Once a release is published that permits Python 3.13, pip on 3.13 will install that newer compatible version normally.

Practical workarounds right now

• Use a Python 3.10–3.12 virtual environment for installing/running the CLI.
• If you want a hard failure in automation (instead of backtracking), pin the version you expect. For example, pip install ms-fabric-cli==1.3.1 will fail on Python 3.13 due to the package’s Python requirement.

Docs action

We’ll update installation/troubleshooting guidance to call this out explicitly (Python version requirement + pip’s backtracking behavior) to prevent future confusion.

[HasanAboShally]

/triaged

[microsoft-github-policy-service]

Triage has been completed for this issue.