feat: Clarify communication rules and document dependency conflict resolution process for improved stakeholder interactions
This commit is contained in:
@@ -89,6 +89,8 @@ Capture the durable release and validation path between XFlow changes and real c
|
||||
- fixed version references in the Podfile when present
|
||||
- archived pipeline artifacts such as `xcarchive` outputs and captured `Podfile.lock` files
|
||||
- Even those checks are not perfect guarantees because the podspec repo can be edited after publication.
|
||||
- A newly published XFlowViewMaker version can still be blocked in Fid4 if downstream podspec constraints in `FTAccountOpen` or `FTTransfer` do not yet accept the new adapter version.
|
||||
- Historical/current evidence suggests Tauf has resolved similar propagation blocks by updating the relevant constraint directly in the podspec repo.
|
||||
|
||||
---
|
||||
|
||||
|
||||
Reference in New Issue
Block a user