<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
    <channel>
        <title>CI/CD - 标签 - Simi Studio</title>
        <link>/tags/ci/cd/</link>
        <description>CI/CD - 标签 - Simi Studio</description>
        <generator>Hugo -- gohugo.io</generator><language>zh-CN</language><managingEditor>simi@simi.studio (Simi)</managingEditor>
            <webMaster>simi@simi.studio (Simi)</webMaster><lastBuildDate>Sun, 22 Nov 2026 10:00:00 &#43;0800</lastBuildDate><atom:link href="/tags/ci/cd/" rel="self" type="application/rss+xml" /><item>
    <title>移动 App 更新日志的工程化工作流</title>
    <link>/posts/mobile-app-release-notes-workflow/</link>
    <pubDate>Sun, 22 Nov 2026 10:00:00 &#43;0800</pubDate>
    <author>simi@simi.studio (Simi)</author>
    <guid>/posts/mobile-app-release-notes-workflow/</guid>
    <description><![CDATA[<p>每次发版前翻几十条 <code>git log</code>，把 <code>fix(db): filter tombstones in aggregate query</code> 翻译成用户能读懂的商店文案，既容易漏掉关键修复，又容易把重构和内部改动混进去；反过来，直接用自动化工具把提交标题拼成发布说明，C 端用户看到的又是一堆晦涩的工程黑话。</p>
<p>本文整理一套适用于 iOS / Android 双端移动 App（尤其是 Monorepo 与高频 Squash Merge 仓库）的更新日志工程方案。基于截至 2026 年 11 月的 <a href="https://keepachangelog.com/en/1.1.0/" target="_blank" rel="noopener noreffer ">Keep a Changelog 1.1.0</a> 原则、Git Trailer 机制与双商店元数据硬约束，拆解方案选型、两层采集与定稿架构、五个最容易踩中的工程边界坑，以及从草稿到 App Store 和 Google Play 定稿的落地规范。</p>]]></description>
</item>
</channel>
</rss>
