|Project Name||Stars||Downloads||Repos Using This||Packages Using This||Most Recent Commit||Total Releases||Latest Release||Open Issues||License||Language|
|:package::rocket: Fully automated version management and package publishing|
|Edk2||3,841||2 days ago||160||other||C|
|Add And Commit||945||5 days ago||8||mit||TypeScript|
|:octocat: Automatically commit changes made in your workflow run directly to your repo|
|Seleniumhq.github.io||699||a day ago||55||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.|
|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 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
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
config options of the @semantic-release/commit-analyzer and @semantic-release/release-notes-generator plugins.
The table below shows which commit message gets you which release type when
semantic-release runs (using the default configuration):
|Commit message||Release type|
(Note that the
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.
For each new commit added to one of the release branches (for example:
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:
After running the tests, the command
semantic-release will execute the following steps:
|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.|
In order to use semantic-release you need:
Let people know that your package is published using semantic-release and which commit-convention is followed by including this badge in your readme.
|Gregor Martynus||Pierre Vanduynslager||Matt Travi|
|Stephan Bönnemann||Rolf Erik Lekang||Johannes Jörg Schmidt||Finn Pauls||Christoph Witzko|