Please stop capping python version

[dbrownems]

Use Case / Problem

It's unlikely python releases will break anything, and it creates time windows where the tool is unnecessarily hard to install. Last month I had to reinstall python two additional times to get to a version that you supported.

Proposed Solution

Allow installation on any later version of python.

Alternatives Considered

No response

Impact Assessment

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

Implementation Attestation

• I understand this feature should maintain backward compatibility (if applicable)
• I understand this feature should not introduce performance regressions for existing workflows
• I acknowledge that new features must follow fabric-cicd's established patterns and conventions

Implementation Notes

No response

[ayeshurun]

/triaged

Hi @dbrownems, thank you for the feedback, and we completely understand the frustration of having to juggle Python versions.

The reason we've historically capped the Python version is that we need to ensure all our upstream dependencies fully support a given Python release before we can certify it.

When a dependency doesn't yet have compatible wheels for a new Python version, users can hit installation failures or subtle runtime issues, which is arguably a worse experience than the version cap itself.

That said, we hear you and we want to minimize these friction windows. We're looking at ways to validate and lift the cap more quickly after new Python releases. We'll also keep this issue open to track progress toward supporting 3.14 once our dependencies are ready.

Thanks again for raising this.

[microsoft-github-policy-service]

Triage has been completed for this issue.