Repository navigation
Publish bounded observation API and current artifact versions - #164
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
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.
Published operator observation
Update the public release manifest to Workflow 2.4.5, PHP SDK 2.2.3, Server 2.5.5 and Waterline 2.2.0. Python, Rust and CLI remain unchanged.
Copy control-plane OpenAPI documentation revision 12 from the published Server source. It documents the bounded run observation and namespace summary reads. Protocol version 2 and its catalog identity remain unchanged.
Related: durable-workflow/waterline#141 and durable-workflow/waterline#142.
Verification
The supporting packages are published. Server publication and all 12 published PHP/Python/Rust lifecycle cells pass. Waterline's merged-source database, Laravel compatibility and UI checks pass. Its stable image publication and final consumer checks are running and must pass before this PR lands.
The normal website checks and Pages deployment verify this change.