Repository navigation
Explain activity argument and result compatibility across deployments - #366
Merged
Merged
Conversation
|
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.
Activity attempts can execute after a deployment with old arguments, and workflow replay can read results written by older activities. The versioning guide now shows additive argument and result examples, explains when to introduce another activity type, and records the observed failure boundaries for embedded PHP and all three SDKs. All eight languages include the same guidance and executable examples.
Published-artifact qualification: twelve SDK originals and source recipes, plus the embedded Workflow 2.11.2 qualification. The guide explicitly identifies the released DTO data-loss behavior tracked in Workflow #910 and does not claim an unpublished safeguard.
Refs #363. Validation: Documentation Qualification 39919465195 builds all eight locales and generated LLM references at the exact head. Source hashes and executable examples match. Real Chromium checks pass English and German navigation to the signal recipe, canonical/alternate links, release-table contents, and 390px light/dark layouts. CodeQL, Sonar, protocol and public-boundary checks pass. Live eight-locale verification follows deployment. The slower duplicate local all-locale build was intentionally stopped after the exact-head CI build passed.