semver-action

Semantic Versioning Action

This action calculates the next version relying on semantic versioning.

Strategies

If auto bump, it will try to extract the closest tag and calculate the next semantic version. If not, it will bump respecting the value passed.

Branch Names

These are the prefixes we expect when auto bump:

• ^bugfix/.* or ^hotfix/.* - patch
• ^doc/.* - build
• ^feature/.* - minor
• ^major/.* - major
• ^misc/.* - build

Scenarios

Auto Bump

• Not a valid source branch prefix - Increments pre-release version.

      v0.1.0 results in v0.1.0-pre.1
      v1.5.3-pre.2 results in v1.5.3-pre.3
  

• Source branch is prefixed with bugfix/ and dest branch is develop - Increments patch version.

  v0.1.0 results in v0.1.1-pre.1
  v1.5.3-pre.2 results in v1.5.4-pre.1
  

• Source branch is prefixed with hotfix/ and dest branch is master - Increments patch version.

  v0.1.0 results in v0.1.1
  v1.5.3-pre.2 results in v1.5.4
  

• Source branch is prefixed with feature/ and dest branch is develop - Increments minor version.

  v0.1.0 results in v0.2.0-pre.1
  v1.5.3-pre.2 results in v1.6.0-pre.1
  

• Source branch is prefixed with major/ and dest branch is develop - Increments major version.

  v0.1.0 results in v1.0.0-pre.1
  v1.5.3-pre.2 results in v2.0.0-pre.1
  

• Source branch is develop and dest branch is master - Takes the closest tag and finalize it.

  v0.1.0 stays v0.1.0
  v1.5.3-pre.2 results in v1.5.3
  

Github Environment Variables

• GITHUB_SHA

Example usage

Basic

Uses auto bump strategy to calculate the next semantic version.

- id: semver-tag
  uses: gandarez/semver-action@vlatest
- name: "Created tag"
  run: echo "tag ${{ steps.semver-tag.outputs.semver_tag }}"

Custom

- id: semver-tag
  uses: gandarez/semver-action@vlatest
  with:
    prefix: ""
    prerelease_id: "alpha"
    main_branch_name: "trunk"
    develop_branch_name: "dev"
    debug: "true"
- name: "Created tag"
  run: echo "tag ${{ steps.semver-tag.outputs.semver_tag }}"

Inputs

Outpus