semantic-release-plus
Fork of Automated semver compliant package publishing to enable additional features
Last updated a month ago by joamos .
MIT · Repository · Bugs · Original npm · Tarball · package.json
$ cnpm install semantic-release-plus 
SYNC missed versions from official npm registry.

???????? semantic-release-plus

Fully automated version management and package publishing

Travis Codecov renovate semantic-release-plus

npm latest version npm next version npm beta version

semantic-release-plus is a drop in replacement for semantic release that adds some enhancements:

  • [X] Filter commit by path commitPaths
  • [ ] Set the logging level
  • [ ] Print the next version only

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.

Trust us, this will change your workflow for the better. – egghead.io

Highlights

How does it work?

Commit message format

semantic-release uses the commit messages to determine the type 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.

Here is an example of the release type that will be done based on a commit messages:

Commit message Release type
fix(pencil): stop graphite breaking when too much pressure applied Patch Release
feat(pencil): add 'graphiteWidth' option Minor Feature Release
perf(pencil): remove graphiteWidth option

BREAKING CHANGE: The graphiteWidth option has been removed.
The default graphite width of 10mm is always used for performance reasons.
Major Breaking Release

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 commits 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:

Documentation

Get help

Badge

Let people know that your package is published using semantic-release by including this badge in your readme.

semantic-release

[![semantic-release](https://img.shields.io/badge/%20%20%F0%9F%93%A6%F0%9F%9A%80-semantic--release-e10079.svg)](https://github.com/semantic-release/semantic-release)

Team

Stephan Bönnemann Rolf Erik Lekang Johannes Jörg Schmidt Gregor Martynus Pierre Vanduynslager Pierre Vanduynslager Christoph Witzko
Stephan Bönnemann Rolf Erik Lekang Johannes Jörg Schmidt Gregor Martynus Finn Pauls Pierre Vanduynslager Christoph Witzko

Kill all humans

Current Tags

  • 17.0.0-beta.3                                ...           beta (4 months ago)
  • 18.0.2                                ...           latest (a month ago)
  • 16.1.0                                ...           next (5 months ago)

17 Versions

  • 18.0.2                                ...           a month ago
  • 18.0.1                                ...           3 months ago
  • 18.0.0                                ...           4 months ago
  • 17.0.2                                ...           4 months ago
  • 17.0.1                                ...           4 months ago
  • 17.0.0                                ...           4 months ago
  • 17.0.0-beta.3                                ...           4 months ago
  • 16.1.0                                ...           5 months ago
  • 17.0.0-beta.2                                ...           5 months ago
  • 16.0.6                                ...           5 months ago
  • 17.0.0-beta.1                                ...           5 months ago
  • 16.0.5                                ...           5 months ago
  • 16.0.4                                ...           6 months ago
  • 16.0.3                                ...           7 months ago
  • 16.0.2                                ...           7 months ago
  • 16.0.1                                ...           7 months ago
  • 16.0.0                                ...           7 months ago
Maintainers (1)
Downloads
Today 0
This Week 0
This Month 0
Last Day 0
Last Week 0
Last Month 28
Dependencies (28)
Dev Dependencies (18)
Dependents (0)
None

Copyright 2014 - 2017 © taobao.org |