Skip to content

Update compatible Python dependencies and GitHub Actions - #664

Closed
Aasav Badera (aasavbadera) wants to merge 2 commits into
Azure:masterfrom
aasavbadera:aasavbadera/dependency-upgrades
Closed

Aasav Badera (aasavbadera) wants to merge 2 commits into
Azure:masterfrom
aasavbadera:aasavbadera/dependency-upgrades

Conversation

@aasavbadera

Copy link
Copy Markdown
Collaborator

Changed

Consolidates the dependency upgrades in #637, #640, #651, #653, #658, #662, and #663 into one review. Also incorporates the overlapping action-pinning change from #655.

Dependency Locked version before Selected version
cryptography 46.0.6 46.0.7
idna 3.10 3.20
ijson 3.4.0 3.5.1 on Python 3.9; 3.6.0 on Python 3.10+
PyJWT 2.12.1 2.15.1
certifi 2025.8.3 2026.10.23
OAuthLib 3.3.1 4.0.1
azure-identity 1.24.0 1.26.0 on Python 3.9; 1.27.0 on Python 3.10+
MSAL 1.34.0b1 1.39.0
actions/checkout 3.7.0 / 4.4.0 7.0.1
github/codeql-action (init, autobuild, analyze) 2.28.1 4.39.3
astral-sh/setup-uv 6.8.0 10.3.3
pypa/gh-action-pypi-publish release/v1.12 1.14.3

All updated GitHub Actions are pinned to verified full-length commit SHAs.

Fixed

  • Regenerate the stale lockfile to reflect the existing 6.0.4 workspace versions and already-declared Azure Identity/MSAL requirements. This does not bump the SDK version.
  • Widen ijson to >=3.4.0,<3.7.0, allowing current compatible releases without excluding the previously supported 3.4 series.

Compatibility

  • Preserve the Python 3.9 minimum, SDK APIs, and existing Azure Storage pins (azure-storage-blob==12.26.0, azure-storage-queue==12.13.0).
  • Select the latest stable releases compatible with the supported runtime matrix, with one intentional hold: cryptography==46.0.7 is the latest 46.x maintenance release. Later majors remove OpenSSL 1.1 support, change key-loading behavior, and remove Intel macOS/32-bit Windows support; adopting them would require a separate compatibility decision.
  • ijson 3.6 and Azure Identity 1.27 require Python 3.10+. Their package metadata selects ijson 3.5.1 and Azure Identity 1.26 on Python 3.9 instead; both dependency sets were tested.
  • OAuthLib 4 includes provider-side breaking changes. Here it is only a transitive quick-start dependency through msrest/requests-oauthlib, not a dependency of either published SDK package. Its bearer-token client integration was exercised without requiring provider migration.
  • Newer action runtimes are used only on the existing GitHub-hosted ubuntu-latest jobs. Workflow triggers, inputs, and the release Python version are unchanged.
  • Lockfile versions describe the development/test environment; existing published dependency ranges remain unchanged apart from the widened ijson range. No new direct pins on transitive dependencies are introduced.

Validation

  • Locked all-packages/all-extras development sync and dependency consistency checks on Python 3.9.25, 3.10.22, 3.11.18, 3.12.10, and 3.13.18.
  • Complete non-E2E suite on each version: 263 passed, 26 skipped per run, on Windows.
  • Additional offline integration checks on all five versions: synchronous/asynchronous JSON parsing with the default and pure-Python backends, actual MSAL certificate-assertion signing and PyJWT RSA verification, OAuth2 bearer authentication through msrest, IDNA encoding/decoding, and CA-bundle loading.
  • Both SDK wheels and source distributions built on Python 3.9; wheel metadata retains Python 3.9 support and the existing storage pins.
  • Ruff formatting and lint, baseline-aware BasedPyright, Actionlint, and git diff --check passed.

Live Azure E2E tests and release publishing were not run locally. The updated Actions require hosted CI validation; no claim of exhaustive customer-environment compatibility is made.

Consolidate dependency upgrades while preserving Python 3.9 support, legacy cryptography compatibility, and existing Azure Storage pins.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: d4838492-f350-4185-b6ae-4f0123ba8604

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

The dependency and GitHub Actions updates have no active review issues.

No open issues 🎉

What changed in this PR

Consolidates dependency and GitHub Actions upgrades for the Azure Kusto Python SDK while preserving Python 3.9 support, existing SDK versions, and Azure Storage pins.

Changes:

  • Refreshes locked dependencies and synchronizes workspace metadata with the existing 6.0.4 versions.
  • Widens ijson support to 3.4–3.6, with Python-compatible versions selected in the lockfile.
  • Upgrades release and CodeQL actions, pinning all updated references to full-length commit SHAs.
File Description
uv.lock Updates dependencies, runtime-specific selections, and workspace metadata.
azure-kusto-data/​pyproject.toml Widens the ijson range to >=3.4.0,<3.7.0.
.github/​workflows/​release.yml Upgrades and pins checkout, uv setup, and publishing actions.
.github/​workflows/​codeql-analysis.yml Upgrades pinned checkout and CodeQL actions.

Review effort: Balanced

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: d4838492-f350-4185-b6ae-4f0123ba8604
@aasavbadera

Copy link
Copy Markdown
Collaborator Author

Superseded by #665 with the same commit and file contents, now using this repository's aasavbadera/dependency-upgrades branch instead of a fork.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔵 Needs a closer look

Major action/runtime upgrades in the release and CodeQL workflows need maintainer confirmation because hosted CI and trusted-publishing validation results are not provided.

No open issues 🎉

Review effort: Balanced

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants