[SergeyMenshykh]

Motivation and Context

The Python 3.10 unit-test and coverage jobs for #14506 fail during dependency installation, before tests run:

• Python Test Coverage
• Python Unit Tests - Python 3.10/Linux/Dapr

Both workflows upgrade dependencies with uv sync -U and select cryptography==50.0.2. Although the release metadata permits Python >=3.9, its published files contain neither a Python 3.10-compatible wheel nor a source distribution. This is independent of the MCP tool-name changes.

Description

Add cryptography!=50.0.2; python_version < '3.11' to the project dependencies and synchronize the lockfile's dependency entries. This preserves Python 3.10 support while leaving Python 3.11 and newer unrestricted. No locked package versions or unrelated artifact metadata change.

Focused validation using the workflows' uv 0.5.x series:

• Lockfile consistency check passed with Python 3.10.
• Linux Python 3.10 all-extras and pandas dependency resolution selected cryptography==50.0.1.
• Linux Python 3.11 all-extras dependency resolution selected cryptography==50.0.2.
• All 18 Python/platform marker cases agreed between the manifest and lockfile, and all transitive package records remained unchanged.
• Repository-compatible Ruff manifest lint and git diff --check passed.

The full unit-test suite was not run; this change only affects dependency selection.

Contribution Checklist

• The code builds clean without any errors or warnings
• The PR follows the SK Contribution Guidelines and the pre-submission formatting script raises no violations
• All unit tests pass, and I have added new tests where possible
• I didn't break anyone 😄

[Copilot]

Copilot review overview

🟢 Approval recommended

The narrow exclusion is consistent between the manifest and lockfile and addresses the reported installation failure.

Review effort: Balanced
Findings: None

What changed in this PR

This PR keeps Python 3.10 dependency installation working by excluding an incompatible cryptography release, without restricting Python 3.11 or newer.

Changes:

• Excludes cryptography==50.0.2 on Python versions below 3.11.
• Synchronizes the lockfile with the new dependency constraint.

File	Description
python/​uv.lock	Records the Python-version-specific cryptography constraint.
python/​pyproject.toml	Adds the exclusion to project dependencies.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[semantic-kernel-automation]

MAF Automated Review — Iteration 1

Result: No findings
Scope: full PR (1 commit(s)): 56eede4aa9ec
Model: gpt-5.6-sol

Overview

The PR adds a Python 3.10-only exclusion for one incompatible cryptography release and synchronizes the generated uv lock metadata. The project Python floor, matching manifest/lock markers, and Python 3.10 upgrade-resolution CI constrain the change as intended, and no Critical, High, or Medium defect was established.

Reviewed the supplied pull-request change set across correctness, security/reliability, architecture, and failure behavior.
No publishable findings remained after source verification for this scope.