Semantic Release
| Project Name | Stars | Downloads | Repos Using This | Packages Using This | Most Recent Commit | Total Releases | Latest Release | Open Issues | License | Language |
|---|---|---|---|---|---|---|---|---|---|---|
| Semantic Release | 18,693 | | 20,127 | 31,138 | a day ago | 366 | July 05, 2023 | 336 | mit | JavaScript |
| :package::rocket: Fully automated version management and package publishing | ||||||||||
| Edk2 | 3,843 | 17 hours ago | 159 | other | C | |||||
| EDK II | ||||||||||
| Add And Commit | 945 | 5 days ago | 8 | mit | TypeScript | |||||
| :octocat: Automatically commit changes made in your workflow run directly to your repo | ||||||||||
| Unit Test Demo | 771 | 10 months ago | 1 | September 24, 2019 | 13 | JavaScript | ||||
| 一步一步介绍如何给项目添加单元测试 | ||||||||||
| Seleniumhq.github.io | 699 | 9 hours ago | 56 | apache-2.0 | HTML | |||||
| Official Selenium website and documentation | ||||||||||
| How To Use Travis Ci | 422 | 5 years ago | 1 | apache-2.0 | Java | |||||
| 如何简单入门持续集成( Travis-CI ) http://travis-ci.org/ | ||||||||||
| Cob | 381 | 3 months ago | 6 | April 20, 2020 | 7 | mit | Go | |||
| Continuous Benchmark for Go Project | ||||||||||
| Golang Monorepo | 330 | 5 months ago | 10 | August 30, 2020 | 3 | mit | Shell | |||
| An example of a golang-based monorepo. | ||||||||||
| Travis Watch | 294 |  | 2 | 2 | 2 years ago | 53 | August 22, 2019 | 7 | mit | JavaScript |
| Stream live travis test results of the current commit to your terminal! | ||||||||||
| Wp Dev Lib | 285 |  | 15 | 6 | a year ago | 23 | October 16, 2020 | 52 | mit | Shell |
| DEPRECATED. Common code used during development of WordPress plugins and themes | ||||||||||
📦🚀 semantic-release
Fully automated version management and package publishing
semantic-release automates the whole package release workflow including: determining the next version number, generating the release notes, and publishing the package.
This removes the immediate connection between human emotions and version numbers, strictly following the Semantic Versioning specification and communicating the impact of changes to consumers.
Trust us, this will change your workflow for the better. – egghead.io
Highlights
- Fully automated release
- Enforce Semantic Versioning specification
- New features and fixes are immediately available to users
- Notify maintainers and users of new releases
- Use formalized commit message convention to document changes in the codebase
- Publish on different distribution channels (such as npm dist-tags) based on git merges
- Integrate with your continuous integration workflow
- Avoid potential errors associated with manual releases
- Support any package managers and languages via plugins
- Simple and reusable configuration via shareable configurations
- Support for npm package provenance that promotes increased supply-chain security via signed attestations on GitHub Actions
How does it work?
Commit message format
semantic-release uses the commit messages to determine the consumer impact of changes in the codebase. Following formalized conventions for commit messages, semantic-release automatically determines the next semantic version number, generates a changelog and publishes the release.
By default, semantic-release uses Angular Commit Message Conventions.
The commit message format can be changed with the preset or config options of the @semantic-release/commit-analyzer and @semantic-release/release-notes-generator plugins.
Tools such as commitizen or commitlint can be used to help contributors and enforce valid commit messages.
The table below shows which commit message gets you which release type when semantic-release runs (using the default configuration):
| Commit message | Release type |
|---|---|
fix(pencil): stop graphite breaking when too much pressure applied |
|
feat(pencil): add 'graphiteWidth' option |
|
perf(pencil): remove graphiteWidth optionBREAKING CHANGE: The graphiteWidth option has been removed.The default graphite width of 10mm is always used for performance reasons.
|
(Note that the BREAKING CHANGE: token must be in the footer of the commit) |
Automation with CI
semantic-release is meant to be executed on the CI environment after every successful build on the release branch. This way no human is directly involved in the release process and the releases are guaranteed to be unromantic and unsentimental.
Triggering a release
For each new commit added to one of the release branches (for example: master, next, beta), with git push or by merging a pull request or merging from another branch, a CI build is triggered and runs the semantic-release command to make a release if there are codebase changes since the last release that affect the package functionalities.
semantic-release offers various ways to control the timing, the content and the audience of published releases. See example workflows in the following recipes:
Release steps
After running the tests, the command semantic-release will execute the following steps:
| Step | Description |
|---|---|
| Verify Conditions | Verify all the conditions to proceed with the release. |
| Get last release | Obtain the commit corresponding to the last release by analyzing Git tags. |
| Analyze commits | Determine the type of release based on the commits added since the last release. |
| Verify release | Verify the release conformity. |
| Generate notes | Generate release notes for the commits added since the last release. |
| Create Git tag | Create a Git tag corresponding to the new release version. |
| Prepare | Prepare the release. |
| Publish | Publish the release. |
| Notify | Notify of new releases or errors. |
Requirements
In order to use semantic-release you need:
- To host your code in a Git repository
- Use a Continuous Integration service that allows you to securely set up credentials
- A Git CLI version that meets our version requirement installed in your Continuous Integration environment
- A Node.js version that meets our version requirement installed in your Continuous Integration environment
Documentation
- Usage
- Extending
- Recipes
- Developer guide
- Support
Get help
Badge
Let people know that your package is published using semantic-release and which commit-convention is followed by including this badge in your readme.
[](https://github.com/semantic-release/semantic-release)
Team
 |
 |
 |
|---|---|---|
| Gregor Martynus | Pierre Vanduynslager | Matt Travi |
Alumni
 |
 |
 |
 |
 |
|---|---|---|---|---|
| Stephan Bönnemann | Rolf Erik Lekang | Johannes Jörg Schmidt | Finn Pauls | Christoph Witzko |
