fix(workflow): preserve WorkWX approval node details - #4977
Merged
leozhang2018 merged 4 commits intoSep 15, 2026
Merged
Conversation
Signed-off-by: Cynthia <chenchen@koderover.com>
Signed-off-by: Cynthia <chenchen@koderover.com>
PetrusZ
reviewed
Sep 14, 2026
Signed-off-by: Cynthia <chenchen@koderover.com>
Signed-off-by: Cynthia <chenchen@koderover.com>
PetrusZ
approved these changes
Sep 14, 2026
leozhang2018
added a commit
that referenced
this pull request
Sep 15, 2026
…tails-release-5.0.0 cp: cherry pick #4977 to release 5.0.0
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
3 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.
What this PR does / Why we need it:
Fixes missing
approval_node_detailsfor WorkWX approval jobs after approval status handling switched to active polling.What is changed and how it works?
Parses approval records from the WorkWX approval detail response, converts them to the existing approval node structure, and persists them only when the details change.
Does this PR introduce a user-facing change?
This change is