git - 使用常规提交更新包版本的好的提交消息是什么？

Question

关注 Conventional Commits什么是最好的 <type>对于关于包版本更改(升级/更新)的提交？
例如:feat: Bump React version to "16.13.1"例如:feat: Upgrade all dependencies

Answer 1

Others: commit types other than fix: and feat: are allowed, for example @commitlint/config-conventional (based on the the Angular convention) recommends chore:, docs:, style:, refactor:, perf:, test:, and others. We also recommend improvement for commits that improve a current implementation without adding a new feature or fixing a bug. Notice these types are not mandated by the conventional commits specification, and have no implicit effect in semantic versioning (unless they include a BREAKING CHANGE, which is NOT recommended). A scope may be provided to a commit’s type, to provide additional contextual information and is contained within parenthesis, e.g., feat(parser): add ability to parse arrays.

来源: https://www.conventionalcommits.org/en/v1.0.0-beta.2/
所以对我来说理想的候选人是 chore: upgrade package dependencies这不能导致任何版本号颠簸。
请注意，升级依赖项可能会也可能不会导致重大更改，这可能会导致提交远远大于 package.json更新。
但是就您的应用程序而言，您的工作是处理那些重大更改而不为用户更改任何内容。所以在这方面我不认为 feat:也不是 fix:是合理的，理想情况下，此提交不会带来任何面向用户的更改。