Add Temporal-backed Java SDK release automation - #2986
Draft
eamsden wants to merge 25 commits into
Draft
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.
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
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.
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?
temporalio/sdkmembers, durable pause/resume/handoff, and scheduled runner recovery.prepare-release.ymlas the only manual release procedure. It takes durable Temporal ownership and refuses to publish Maven after automatic Maven submission has started.Why?
The current Actions-only process loses orchestration state with its runner. Temporal keeps control state durable; GitHub Actions artifacts hold transient binary payloads so later jobs can resume the exact release.
Sonatype cannot atomically create a staging repository and persist its ID in Temporal. An ambiguous creation therefore stops for inspection and explicit authorization before another submission generation.
Breaking changes?
No SDK API changes. The automation remains inactive until its Temporal Cloud, GitHub environment, signing, and Maven Central settings are configured.
Server PR
None.
No release, test release, Maven publication, tag push, or GitHub release was performed while testing this change.