版本管理与 API 稳定性
管理破坏性变更和公共 API 契约
版本管理与 API 稳定性 是 CoddyKit 上的免费 Kotlin Multiplatform Academy 课时。 这是第 3 节课，共 4 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 Kotlin Multiplatform Academy 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 Kotlin Multiplatform Academy 课程共包含 4 节课。
本课时的部分内容尚未翻译，以英文显示。
A Version Is a Promise
When teams depend on your library, your version number tells them what to expect from an upgrade. Treat it as a contract, not a guess. 🤝
Semantic Versioning
SemVer uses three numbers: major, minor, and patch. Each part signals a different kind of change to anyone depending on your code.
version = "2.4.1"Patch for Fixes
Bump the patch number for backward-compatible bug fixes. Consumers can upgrade freely with no code changes on their side.
Minor for Features
Raise the minor number when you add new functionality without breaking anything. Old call sites keep working as before.
Major for Breaks
Increase the major number for any breaking change. This warns both teams that upgrading may require edits to their code.
Your Public API Is the Line
Stability is judged by your public surface. Renaming a public function breaks callers, but changing a private helper does not.
Hide What May Change
Mark unstable code internal so it stays out of the contract. You can refactor it freely without bumping the major version.
internal fun buildCache() { }Deprecate Before Removing
Give callers a soft landing with @Deprecated. They keep building, see a warning, and get told what to use instead.
@Deprecated("Use greet(name)")
fun greeting() = greet("there")Suggest a Replacement
Pair the deprecation with a ReplaceWith hint so the IDE can auto-fix old call sites. Migration becomes a single click.
@Deprecated("Renamed", ReplaceWith("greet(name)"))Watch for Accidental Breaks
Even reordering parameters can break Swift callers. Track your API with a dump tool so surprise changes get caught in review.
Keep a Changelog
A clear changelog lists what changed per version. Both Android and iOS teams plan upgrades with confidence instead of fear.
Quick Check
Let's check your versioning instincts.
Recap
Follow SemVer, guard your public API, hide unstable code as internal, deprecate kindly, and keep a changelog both teams trust. 🎉
常见问题解答
「版本管理与 API 稳定性」课时是免费的吗？
是的 — 「版本管理与 API 稳定性」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Kotlin Multiplatform Academy 课程的其余内容，请升级到 CoddyKit PRO。 Kotlin Multiplatform Academy 课程共包含 4 节课。
「版本管理与 API 稳定性」这节课中我会学到什么？
管理破坏性变更和公共 API 契约 你通过在浏览器中直接运行的动手代码来练习 Kotlin Multiplatform Academy，全天候 AI 导师会在你学习这节课的过程中回答你的问题。
学习 Kotlin Multiplatform Academy 需要有经验吗？
无需任何先前经验。CoddyKit 上的 Kotlin Multiplatform Academy 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。 这是第 3 节课，共 4 节。
「版本管理与 API 稳定性」课时需要多长时间？
大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。
我能在这节 Kotlin Multiplatform Academy 课中编写并运行代码吗？
能。每节 Kotlin Multiplatform Academy 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。