Semantic Versioning_this correlates with minor in semantic versioning-优快云博客

本文链接：https://blog.youkuaiyun.com/power_to_go/article/details/103287548

本文探讨了语义版本控制（SemVer）在软件开发中的应用，详细解释了MAJOR、MINOR和PATCH版本号的含义及更新规则。通过实例展示了如何在包管理文件中正确使用版本范围来确保向后兼容性。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

软件版本如何表示的问题

引入 Rust 依赖发现的版本如何表示

Cargo understands Semantic Versioning (sometimes called SemVer), which is a standard for writing version numbers. The number 0.3.14 is actually shorthand for ^0.3.14, which means “any version that has a public API compatible with version 0.3.14.”

具体的表示含义

Given a version number MAJOR.MINOR.PATCH,

increment the:MAJOR version when you make incompatible API changes, 不兼容的API发生改变，增加 MAJOR version。
MINOR version when you add functionality in a backwards compatible manner, 向后兼容的方式添加新的功能
PATCH version when you make backwards compatible bug fixes. 修复向后兼容的 bug
Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.

package.json 中的 npm 依赖

"dependencies": {
  "ant-design-vue": "^1.3.2",
  "apexcharts": "^2.6.0",
  "axios": "^0.18.0",
  "date-fns": "^1.29.0",
  "enquire.js": "^2.1.6",
  "vue": "^2.6.8",
  "vue-apexcharts": "^1.2.7",
  "vue-router": "^3.0.1",
  "vue-video-player": "^5.0.2",
  "vuedraggable": "^2.16.0",
  "vuex": "^3.0.1",
  "webpack-dev-server": "^2.11.5"
}