You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
ci: replace the OTel reference fixture pin after Python PR #796 merges #171
The OTel self-test workflow defaults to Python SDK commit 68f4bdc2ad9bfe8efa4241de4ad3cc3bb889f209, a reference fixture supplied by the still-open aws/aws-durable-execution-sdk-python#796. Track migration to an immutable commit on SDK main once the companion handlers and fixes have merged.
.github/workflows/opentelemetry-conformance-tests.yml on main 9a5ead5e9ab8051bedfd300726472cbd443923cb still uses that SHA as the default sdk_ref.
Python PR #796 is open.
The workflow intentionally pins handlers implementing the full 27-case catalog so conformance changes can merge before their companion SDK work.
During validation on 2026-10-26, the pinned SHA was already absent from #796's then-current head ancestry, but a fresh git fetch --depth=1 of the exact SHA succeeded. A force-push does not automatically make this checkout fail. This is a maintenance follow-up, not a confirmed CI outage.
Acceptance criteria
Document the migration condition next to the pin: replace it with a main-branch SHA after Python #796 and its required companion work merge.
Once that condition is met, choose an immutable SDK main commit containing all required handlers and fixes; update the default sdk_ref and the surrounding reference-fixture comments.
Preserve the manual sdk_ref override.
Run the ordinary OTel execution/invocation suites against the replacement commit and confirm the 27-case catalog remains covered without lowering the coverage threshold or weakening requirements.
Do not switch to a moving main ref or to an older merged commit that lacks the required cases merely to remove the PR-branch dependency.
Activity