Repository navigation
Document pending activity SDK and application upgrades - #205
Merged
Merged
Conversation
This was referenced Oct 19, 2026
Merged
…lication-upgrades
…lication-upgrades
|
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
2 participants
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.
Change
Document the pending remote-activity SDK/application upgrade command from durable-workflow/sample-app#261 in the existing conformance runbook and SDK coverage inventory.
It defines eighteen separate actual outcomes across all nine workflow/activity directions, selected previous/current packages, unchanged original histories/markers/policies/identities, stable Python definition binding and typed results. It distinguishes an activity still unstarted at replacement from callbacks interrupted during an upgrade and from external-effect recovery.
Related work: #122. Other audit acceptance remains open. This guide documents the Sample implementation's exact published-package qualification. Source tests are not actual package replay.
Verification
Reviewed command, environment variable, documentation anchor and assertions against merged Sample
7c0d10ec85c38bbd50b3ad3c475b985f5acb0055/ whole5201671738564a08884de4a6b3eeae2d948c64d1, identical to its reviewed candidate. All 23 Sample candidate checks pass. Independent main39276068981 also passes all eighteen fresh installed-package originals; complete log review verifies the six packages, both nine-direction phases, typed results, original identities/policies and cleanup. The first failed package run remains failed and separate.Updated guide head
db6caf48cba0f29382e75279156f275da8af9b09/ wholecb539696d3bd3a9e8ae8cf6a22ca3743ff744f90incorporates the separately qualified security-maintainer statement and private-reporting directions from current main without changing their bytes. All three exact-head guide checks PASS; synthetic7c51fcbd has the identical whole tree. Earlier passing checks are kept separate.The guide's acceptance is its exact command's independent main execution plus these repository checks. Sample's separate ordinary forty-case timer main profile39276069008 remains running (19/20 checks pass) and retains its own outcome on Sample261; publishing these two documentation files makes no full-Sample-matrix claim.
Merged as
5b703874d13f40a9da867400006fc4c6953711dcwith the identical reviewed tree. The completed remote branch is deleted; public runbook, coverage row and linked Sample anchor are visible. All three independent main checks PASS, including repository39279322238/Sonar39279322133. Sample's separate timer original also completes successfully; all20 of its main checks now PASS. Historical failures retain their original outcomes.