semantic-release
semantic-release is an automated version management and package publishing tool that determines version numbers and publishes based on commit messages.
Timeline (last 90 days)
In the Git and package management ecosystem, the term "bump" specifically refers to the act of raising a version number, commonly seen in automation tools such as npm version, bumpversion, and semantic-release.
Monorepo projects usually introduce automated versioning tools (such as Changesets, semantic-release or lerna) together with CI pipelines, so that after commits are merged into the main branch, the version number is automatically calculated, a Git tag is created and the release is published.
CI/CD automatic publishing means that after code is merged into the main branch, the pipeline automatically advances the version number (usually with tools such as changesets and semantic-release), generates a changelog, tags and publishes to npm.
Hosted changelog tools such as release-drafter, semantic-release and changesets rely on commit conventions (such as the BREAKING CHANGE: footer and the feat!: prefix) to generate changelogs.
github-actions automatic publishing usually relies on GitHub's OIDC and npm's provenance mechanism, and the publishing pipeline is generally triggered by changesets or semantic-release.
The automated pipeline adopted by Cline is often paired with Changesets or semantic-release tools, which automatically infer the version number from commit information, generate a changelog, and submit a PR.
Automated release patterns such as Changesets or semantic-release have been validated and used by mainstream open source projects such as Vite, Vitest, and Turborepo.
All Facts (9)
根据语义化版本规则，fix类型提交触发PATCH版本递增，feat类型触发MINOR递增，包含BREAKING CHANGE的提交触发MAJOR递增
95%Unverifiedsemantic-release等自动化发布工具完全依赖规范化的提交信息来决策版本号
90%UnverifiedIn the Git and package management ecosystem, the term "bump" specifically refers to the act of raising a version number, commonly seen in automation tools such as npm version, bumpversion, and semantic-release.
50%UnverifiedMonorepo projects usually introduce automated versioning tools (such as Changesets, semantic-release or lerna) together with CI pipelines, so that after commits are merged into the main branch, the version number is automatically calculated, a Git tag is created and the release is published.
50%UnverifiedCI/CD automatic publishing means that after code is merged into the main branch, the pipeline automatically advances the version number (usually with tools such as changesets and semantic-release), generates a changelog, tags and publishes to npm.
50%UnverifiedHosted changelog tools such as release-drafter, semantic-release and changesets rely on commit conventions (such as the BREAKING CHANGE: footer and the feat!: prefix) to generate changelogs.
50%Unverifiedgithub-actions automatic publishing usually relies on GitHub's OIDC and npm's provenance mechanism, and the publishing pipeline is generally triggered by changesets or semantic-release.
50%UnverifiedAutomated release patterns such as Changesets or semantic-release have been validated and used by mainstream open source projects such as Vite, Vitest, and Turborepo.
50%UnverifiedThe automated pipeline adopted by Cline is often paired with Changesets or semantic-release tools, which automatically infer the version number from commit information, generate a changelog, and submit a PR.
50%