david.delagneau/fidelity-ai-workspace
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: Clarify communication rules and document dependency conflict resolution process for improved stakeholder interactions

Browse Source
This commit is contained in:
David Delagneau
2026-04-17 10:06:45 -06:00
parent 83d91ed19a
commit 01f0a6bd33
4 changed files with 23 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
vault/02-work-items/pdiap-15765.md
View File

@@ -70,9 +70,10 @@ tags:
## Next Step
- Get the remaining FTFrameworks code-owner approval on the XFlowViewMaker follow-up PR.
- After merge, let `publish-XFlowViewMaker` release the updated adapter version.
- Update the Fid4 Podfile in `ap010981-ios-flagship-app`, run `tuist generate -n` and `pod install --repo-update`, then open the consumer PR.
- The XFlowViewMaker approval and publish step are now complete.
- Resolve the new Fid4 dependency conflict caused by downstream `FTAccountOpen` / `FTTransfer` constraints that do not yet accept the published XFlowViewMaker version.
- Ask Tauf to remind David of the exact podspec-constraint fix path used in similar cases, then document that process for future reuse.
- After the dependency constraint issue is resolved, update the Fid4 Podfile in `ap010981-ios-flagship-app`, run `tuist generate -n` and `pod install --repo-update`, then open the consumer PR.
- After the Fid4 PR merges, treat the app release as the final downstream step before broader user visibility.
- Keep the separate `HybridBrokerageAccountOpening` / `JointIdentityCheck` scenario out of the client-fix scope unless later evidence proves it is part of the same issue.
- Consider a separate follow-up ticket for the cross-platform service-side issue if that path still stands after consumer confirmation.