Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/christian-draeger/increment-semantic-version
https://github.com/christian-draeger/increment-semantic-version
Last synced: 12 days ago
JSON representation
- Host: GitHub
- URL: https://github.com/christian-draeger/increment-semantic-version
- Owner: christian-draeger
- License: mit
- Created: 2020-01-17T19:53:24.000Z (over 4 years ago)
- Default Branch: master
- Last Pushed: 2023-01-27T13:31:27.000Z (over 1 year ago)
- Last Synced: 2024-05-03T02:25:23.966Z (20 days ago)
- Language: Shell
- Size: 22.5 KB
- Stars: 84
- Watchers: 2
- Forks: 23
- Open Issues: 4
-
Metadata Files:
- Readme: README.md
- Funding: .github/FUNDING.yml
- License: LICENSE
Lists
- awesome-workflows - Increment Semantic Version - Bump a given semantic version (SemVer), depending on given release type. (Community Resources / Utility)
- awesome-actions - Increment Semantic Version - Bump a given semantic version (SemVer), depending on given release type. (Community Resources / Utility)
- awesome-actions - Increment Semantic Version - Bump a given semantic version (SemVer), depending on given release type. (Community Resources / Utility)
- fucking-awesome-actions - Increment Semantic Version - Bump a given semantic version (SemVer), depending on given release type. (Community Resources / Utility)
- awesome-actions-fork - Increment Semantic Version - Bump a given semantic version (SemVer), depending on given release type. (Community Resources / Utility)
- awesome-actions - Increment Semantic Version - Bump a given semantic version (SemVer), depending on given release type. (Community Resources / Utility)
- awesome-actions - Increment Semantic Version - Bump a given semantic version (SemVer), depending on given release type. (Community Resources / Utility)
README
# Increment Semantic Version
This is a GitHub action to bump a given semantic version, depending on a given version fragment.
## Inputs
### `current-version`
**Required** The current semantic version you want to increment. (e.g. 3.12.5)
### `version-fragment`
**Required** The versions fragment you want to increment.
Possible options are **[ major | feature | bug | alpha | beta | pre | rc ]**
## Outputs
### `next-version`
The incremented version.
## Example usage
- name: Bump release version
id: bump_version
uses: christian-draeger/[email protected]
with:
current-version: '2.11.7-alpha.3' # also accepted: 'v2.11.7-alpha.3' | '2.11.7-alpha3'
version-fragment: 'feature'
- name: Do something with your bumped release version
run: echo ${{ steps.bump_version.outputs.next-version }}
# will print 2.12.0
## input / output Examples
| version-fragment | current-version | | output |
| ---------------- | --------------- | - | -------------- |
| major | 2.11.7 | | 3.0.0 |
| major | v2.11.7 | | 3.0.0 |
| major | 2.11.7-alpha3 | | 3.0.0 |
| major | 2.11.7-alpha.3 | | 3.0.0 |
| feature | 2.11.7 | | 2.12.0 |
| feature | 2.11.7-alpha3 | | 2.12.0 |
| feature | 2.11.7-alpha.3 | | 2.12.0 |
| bug | 2.11.7 | | 2.11.8 |
| bug | 2.11.7-alpha3 | | 2.11.8 |
| bug | 2.11.7-alpha.3 | | 2.11.8 |
| alpha | 2.11.7 | | 2.11.7-alpha.1 |
| alpha | 2.11.7-alpha3 | | 2.11.7-alpha.4 |
| alpha | 2.11.7-alpha.3 | | 2.11.7-alpha.4 |
| beta | 2.11.7 | | 2.11.7-beta.1 |
| beta | 2.11.7-alpha3 | | 2.11.7-beta.1 |
| beta | 2.11.7-alpha.3 | | 2.11.7-beta.1 |
| pre | 2.11.7 | | 2.11.7-pre.1 |
| pre | 2.11.7-alpha3 | | 2.11.7-pre.1 |
| pre | 2.11.7-alpha.3 | | 2.11.7-pre.1 |
| rc | 2.11.7 | | 2.11.7-rc.1 |
| rc | 2.11.7-alpha3 | | 2.11.7-rc.1 |
| rc | 2.11.7-alpha.3 | | 2.11.7-rc.1 |
# License
The scripts and documentation in this project are released under the [MIT License](LICENSE)