Add concise Temporal-backed Python release automation - #2995
Open
eamsden wants to merge 37 commits into
Open
Conversation
Orchestrate immutable sdk-java release candidates with transient GitHub Actions Workers, a no-input approval Update, privileged publication queues, and exact-state external reconciliation.
Make release progress explicitly staged and controllable, bind approval to a locked release-specific GitHub issue, and make Maven and GitHub publication reconciliation safe across ambiguous retries. Add a durable emergency handoff path, frozen Worker routing, prompt Activity cancellation, idempotent native builds, and focused local tests.
Harden the Temporal state machine, publication reconciliation, approval recovery, and transient Worker behavior. Add protected Maven generation authorization, draft-first exact asset handling, maintenance-branch recovery, and both automated and independent emergency paths.
Bind release workflows to the exact receipted Candidate run, separate candidate compilation from credentialed artifact storage, adopt fallback artifacts across reruns, and classify S3 absence without masking service failures.
eamsden
force-pushed
the
eamsden/temporal-release-automation-python
branch
from
August 10, 2026 19:35
fa2ee95 to
551ff6c
Compare
eamsden
marked this pull request as ready for review
August 10, 2026 19:36
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
1 participant
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.
What changed?
The measured release-automation surface is 3,506 lines across 20 files, down from 7,548 lines across 34 files at the initial Python checkpoint. Excluding tests and the generated lockfile, the authored operational surface is 2,819 lines.
Why?
This is the smaller Python alternative to #2986. It preserves Temporal-backed orchestration and the hard Maven/GitHub reconciliation boundaries while removing approval, ownership, handoff, redundant manifests, duplicate validation, Java/Gradle scaffolding, unnecessary Actions glue, and scheduled polling.
Breaking changes?
No SDK API changes. Release operations remain inactive until the required Temporal deployment, GitHub App, signing, and Maven credentials are configured.
The former manual
prepare-release.ymlpath is intentionally removed. Merging a valid release-note file is the release authorization and execution trigger.Verification
uv lock --checkNo release, test release, Maven publication, tag, GitHub release, or external Temporal operation was run while developing or testing this change.
Server PR
None.
Supersedes #2986.