Repository navigation
ci: publish emulator images after pypi packages - #805
Merged
Merged
Conversation
yaythomas
approved these changes
Oct 22, 2026
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The testing 1.3.0 image release failed because its Docker build tried to install
aws-durable-execution-sdk-python>=2.1.0about ten seconds before the SDK wheel reached PyPI. Both release workflows started independently onrelease.published.Make the ECR workflow reusable and call it only after the PyPI publishing matrix succeeds. Pass the original release tag and the ECR role explicitly, preserving the existing version checks, serialized image releases, and recovery behavior. Failed image jobs can be rerun within the same release run after PyPI publishing has succeeded. Add regression coverage for ordering, tag propagation, and permissions, and run it when either release workflow changes.
Validation:
hatch run dev-testing:python -m pytest .github/scripts/tests: 234 passed, including the new regression tests and existing ECR publication/recovery tests. One unrelated failure,test_lintcommit.py::test_subject_uppercase, also reproduces with unchanged files from main.hatch fmt --check .github/scripts/tests/test_release_workflow_dependencies.py: passed.concurrency.queuediagnostic excluded; the same diagnostic occurs on main.git diff --check: passed.Live PyPI/ECR publishing was not run as part of validation.