Skip to content

[python] avoid etag/match_condition clientName collision with multiple etag headers #215

[python] avoid etag/match_condition clientName collision with multiple etag headers

[python] avoid etag/match_condition clientName collision with multiple etag headers #215

Triggered via pull request May 28, 2026 16:45
Status Cancelled
Total duration 5m 4s
Artifacts

python-integration.yml

on: pull_request
Build & Regenerate
4m 4s
Build & Regenerate
Mock API Tests
0s
Mock API Tests
Type Checking
0s
Type Checking
Lint & Format
0s
Lint & Format
Docs Validation
0s
Docs Validation
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 1 warning
Build & Regenerate
Canceling since a higher priority waiting request for Python Integration-refs/pull/10816/merge exists
Build & Regenerate
The operation was canceled.
Python Integration
Canceling since a higher priority waiting request for Python Integration-refs/pull/10816/merge exists
Build & Regenerate
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4, pnpm/action-setup@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/