Merged Is Not Shipped: Why a Year-Old Fix Never Reached You

说明与用途

合并修复并不意味着修复已交付；如果依赖被固定在旧提交，需手动更新指针以实现交付。

问题

A bug fix was merged upstream but never reached end‑users because dependency pins (git submodules, lockfiles, etc.) were not advanced.

结果

The fix was never shipped to iOS users because the submodule pointer was not advanced; the issue persisted for a year.

工作流

• 1. Identify the bug in user reports. 2. Search upstream repository for a fix commit. 3. Compare the fix commit SHA with the pinned commit in the client. 4. Count commits behind to assess gap. 5. If the fix is present, cherry‑pick or bump the submodule pointer. 6. Rebuild and test the client. 7. Publish updated build or create a pull request for the pointer update.
• 8. Monitor for future fixes and automate pin updates.

证据

The iOS client's pointer was two dozen commits behind the fix.

来源

The fix landed in the library. Then look at where the three clients had their submodule pinned:

来源