-
[OPIK-4913] [INFRA] Rename SDK E2E test workflow to clarify it's Python-specific (#5638)
frostbyte_neo 发布于
2026-03-12 10:18:57 +00:00 - [OPIK-4913] [INFRA] Rename SDK E2E test workflow to clarify it's Python-specific
Rename sdk-e2e-tests.yaml to python_sdk_e2e_tests.yml and update all
references (name, run-name, job name, check_name, self-referencing paths)
to include "Python". Add matrix.python_version to check_name to
distinguish test results per Python version.Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com
- [OPIK-4913] [INFRA] Align Publish Test Report behavior across SDK E2E workflows
Change Python SDK from if: failure() to if: always() and add
action_fail: true to TypeScript SDK, so both match the backend
workflow behavior: always publish results, fail check on test failure.Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com
- [OPIK-4913] [INFRA] Fix Python SDK unit tests workflow naming and test report behavior
Update python_sdk_unit_tests.yml to use "Python SDK" prefix in all
display names, add Python version to check_name, change Publish Test
Report from if: failure() to if: always(), and add missing permissions
for checks and pull-requests.Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com
- [OPIK-4913] [INFRA] Add self-reference path trigger to Python SDK unit tests workflow
Without this, changes to the workflow file itself don't trigger a run,
making it impossible to verify workflow changes on PRs.Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com
- [OPIK-4913] [INFRA] Add missing permissions and self-reference path to Python backend tests
Add checks: write and pull-requests: write permissions required by
publish-unit-test-result-action, and add self-reference path trigger
so workflow changes trigger a run for verification.Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com
Co-authored-by: Claude Opus 4.6 noreply@anthropic.com
下载附件