feat: Clarify code-owner approval requirements for PDIAP-15765 in documentation
This commit is contained in:
@@ -22,7 +22,7 @@ tags:
|
||||
- Active closeout
|
||||
- Small XFlowSDK compatibility fix merged and released in XFlow `2.8.48`
|
||||
- XFlowViewMaker was updated to the new XFlow version and a follow-up PR was opened
|
||||
- The XFlowViewMaker PR already has some approvals, but one code-owner approval is still required before merge
|
||||
- The XFlowViewMaker PR already has some approvals, but one FTFrameworks code-owner approval is still required before merge
|
||||
|
||||
---
|
||||
|
||||
@@ -70,7 +70,7 @@ tags:
|
||||
|
||||
## Next Step
|
||||
|
||||
- Get the remaining code-owner approval on the XFlowViewMaker follow-up PR.
|
||||
- Get the remaining FTFrameworks code-owner approval on the XFlowViewMaker follow-up PR.
|
||||
- Run the remaining pipeline/release steps after the PR merges.
|
||||
- Update Fid4 so the released XFlow `2.8.48` change propagates through the consumer path.
|
||||
- Keep the separate `HybridBrokerageAccountOpening` / `JointIdentityCheck` scenario out of the client-fix scope unless later evidence proves it is part of the same issue.
|
||||
|
||||
Reference in New Issue
Block a user