[FEATURE] support python 3.14

[hutch3232]

Use Case / Problem

In this comment: #89 (comment) python 3.14 was said to be unavailable because a dependency (msal) did not support it.

msal added python 3.14 support ~3 months ago: https://github.com/AzureAD/microsoft-authentication-library-for-python/releases/tag/1.35.0

Proposed Solution

I think the python version upper bound should be removed entirely. I don't think it is good practice to include that - especially when the reasoning is due to dependencies.

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

[microsoft-github-policy-service]

Thank you for submitting this issue, Paul (@hutch3232).
A member of the Fabric CLI team will review your submission and provide feedback shortly.

[github-actions]

AI Assessment: Help Wanted

This is a reasonable request following recent dependency updates. Now that msal supports Python 3.14, the upper bound restriction in the package metadata can be relaxed or removed, enabling users to install ms-fabric-cli on Python 3.14. This aligns with standard Python packaging practices (PEP 440) and benefits users seeking platform parity and future-proofing.

For implementation, update the python_requires argument in setup.py/pyproject.toml to remove any explicit <3.14 upper bound. Validate that the CLI works under Python 3.14 by running the existing test suite locally (or in CI, if configured). If any code or dependencies explicitly block 3.14, note the failures or submit fixes upstream.

This change is unlikely to introduce backwards incompatibility and matches other modern Python CLI projects in approach.

Next Steps

🤝 Community contribution welcome — This feature is well-scoped for a community contributor. See implementation guidance above.

---

💡 If this issue requires the team's attention and was not escalated, you can tag @microsoft/fabric-cli-dev to notify the team.

[algojogacor]

I would like to work on this. The approach:

1. Remove the <3.14 upper bound from requires-python in pyproject.toml (was ">=3.10,<3.14" → ">=3.10")
2. Add Python 3.14 to the classifiers list
3. The msal dependency already supports 3.14 (since v1.35.0)

The msal upper bound was the original blocker (re: #89), and it has been resolved for ~3 months now. Removing the upper bound altogether follows PEP 440 best practices — upper bounds on python_requires are discouraged unless there is a known incompatibility, which no longer applies here.

I will have a PR ready shortly.