使用常规提交更新包版本的好的提交消息是什么？
What would be a good commit message for updating package versions using Conventional Commits?
在 Conventional Commits 之后什么是关于包版本更改 (upgrades/updates) 的最佳 <type> 提交？
例如：feat: Bump React version to "16.13.1"
例如：feat: Upgrade all dependencies
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: 都不合理，因为 理想情况下 ，此提交不会带来任何面向用户的更改。
如果您使用 build 范围，请考虑此选项：
build(deps): Bump React version to "17.0.2"
常规提交基于Angular 常规提交。 Angular 的 CONTRIBUTING.md 状态：
build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
在 Conventional Commits 之后什么是关于包版本更改 (upgrades/updates) 的最佳 <type> 提交？
例如：feat: Bump React version to "16.13.1"
例如：feat: Upgrade all dependencies
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: 都不合理，因为 理想情况下 ，此提交不会带来任何面向用户的更改。
如果您使用 build 范围，请考虑此选项：
build(deps): Bump React version to "17.0.2"
常规提交基于Angular 常规提交。 Angular 的 CONTRIBUTING.md 状态：
build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)