Repository navigation
CHORE: Bump PyJWT to 2.15.0 in release dependency locks - #831
Conversation
|
Azure Pipelines: There may be pipelines that require an authorized user to comment /azp run to run. |
PR Performance Report✅ No regression detectedNo consistent slowdowns detected across all 2 environments. 0 IMPROVEMENTS 0 SLOWDOWNS 2/2 ENVIRONMENTS Coverage: 2 of 2 environments completed. Advisory result; does not block merging. Performance diagnosticsPhase times are inclusive diagnostics and must not be added together. They identify where measured time changed, not why it changed. No affected phases or call-count changes were recorded. All database tasks and timingsUnix / SQL Server 2022
Unix / SQL Server 2025
Build and measurement detailsPR head:
A consistent change requires more than 20% median paired movement, at least 1 ms between the median runtimes, and at least 80% of pairs exceeding the relative threshold in the same direction. A slowdown without enough pair agreement is reported as inconsistent. The displayed change is the median of paired before-and-after ratios. It is not recalculated from the two displayed median runtimes. Both revisions use profiling-enabled builds on the same agent and database, with alternating order and discarded warmups. Results are diagnostic and do not represent production-wheel latency. Raw samples and logs are attached to the ADO run as |
There was a problem hiding this comment.
Copilot review overview
🟡 Changes recommended
Both regenerated locks omit required Python 3.10 dependencies and directly requested build tools.
Review effort: Balanced
Findings: None
What changed in this PR
Updates PyJWT in hash-locked Linux test and macOS build environments.
Changes:
- Bumps PyJWT from 2.13.0 to 2.15.0 with updated hashes.
- Regenerates dependency metadata and closures.
| File | Description |
|---|---|
eng/requirements-test-linux.txt |
Updates the Linux test lock. |
eng/requirements-build-macos.txt |
Updates the macOS build lock. |
💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
4d2508d to
e9f818a
Compare
Bumps [pyjwt](https://github.com/jpadilla/pyjwt) from 2.13.0 to 2.15.0. - [Release notes](https://github.com/jpadilla/pyjwt/releases) - [Changelog](https://github.com/jpadilla/pyjwt/blob/master/CHANGELOG.rst) - [Commits](jpadilla/pyjwt@2.13.0...2.15.0) --- updated-dependencies: - dependency-name: pyjwt dependency-version: 2.15.0 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
e9f818a to
e681c8e
Compare
Resolve generated lock conflicts against current main with uv 0.12.6. Retain all current pins and universal markers while upgrading PyJWT to 2.15.0. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
🔵 Needs a closer look
Offline review cannot verify PyJWT 2.15.0’s publication, artifact hashes, or compatibility with MSAL and supported Python versions, so dependency-refresh regeneration and release-matrix validation results need confirmation.
No open issues 🎉
Review effort: Balanced
📊 Code Coverage Report
Diff CoverageDiff: main...HEAD, staged and unstaged changesNo lines with coverage information in this diff. 📋 Files Needing Attention📉 Files with overall lowest coverage (click to expand)mssql_python.pybind.performance_counter.hpp: 0.7%
mssql_python.pybind.logger_bridge.cpp: 57.9%
mssql_python.pybind.ddbc_bindings.h: 64.5%
mssql_python.pybind.logger_bridge.hpp: 70.8%
mssql_python._native_fetch.py: 77.7%
mssql_python.__init__.py: 80.8%
mssql_python.pybind.ddbc_bindings.cpp: 81.4%
mssql_python.pybind.row_mapping_cache.hpp: 81.5%
mssql_python.pybind.connection.connection_pool.cpp: 82.5%
mssql_python.pybind.connection.connection.cpp: 83.1%🔗 Quick Links
|
Retain reproducible universal PyJWT 2.15.0 locks with all other pins and markers unchanged. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
|
/azp run MSSQL-Python-PR-Validation |
|
Azure Pipelines: Successfully started running 1 pipeline(s). |
Jahnvi Thakkar (jahnvi480)
left a comment
There was a problem hiding this comment.
The reviewed PyJWT-only lock update preserves the dependency closure and markers. Azure build 191864 now passed all 23 jobs, including both previously failing Windows and macOS jobs on their bounded retries. Both exact-head paired Linux SQL Server performance reports validated without a consistent regression under the existing policy; these profiling-enabled results are not a zero-effect or universal release-latency guarantee.
Merge main without rewriting history; retain only the two universal PyJWT 2.15.0 version/hash lock updates relative to main. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
|
/azp run MSSQL-Python-PR-Validation |
|
Azure Pipelines: Successfully started running 1 pipeline(s). |
|
/azp run MSSQL-Python-PR-Validation |
|
Azure Pipelines: Successfully started running 1 pipeline(s). |
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
|
/azp run MSSQL-Python-PR-Validation |
|
Azure Pipelines: Successfully started running 1 pipeline(s). |
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
|
/azp run MSSQL-Python-PR-Validation |
|
Azure Pipelines: Successfully started running 1 pipeline(s). |
Work Item / Issue Reference
Summary
Upgrade PyJWT from 2.13.0 to 2.15.0 in the release build/test dependency locks rather than removing the package. Resolve conflicts against current main and regenerate complete, hash-locked universal dependency closures, retaining required build tools, test dependencies, and supported Python/platform markers.