You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|`tag-prefix`| false |`v`| By default the action strips the prefixes off, but any value provided here will be prepended to the next calculated version.<br/><br/>GitHub indicates it is common practice to prefix your version names with the letter `v` (which is the default). If you do not want a prefix use `tag-prefix: none`. |
65
65
|`fallback-to-no-prefix-search`| false |`true`| Flag indicating whether it should fallback to a prefix-less search if no tags are found with the current prefix. Helpful when starting to use prefixes with tags. Accepted values: true\|false. |
66
66
|`calculate-prerelease-version`| false |`false`| Flag indicating whether to calculate a pre-release version rather than a release version. Accepts: `true\|false`. |
@@ -71,17 +71,19 @@ If none of the previous patterns match, the action will increment the patch vers
71
71
72
72
Each of the outputs are available as environment variables and as action outputs.
|`NEXT_VERSION`| The next `major.minor.patch` version |
77
+
|`NEXT_VERSION_NO_PREFIX`| The next `major.minor.patch` version without the tag prefix |
78
+
|`NEXT_MINOR_VERSION`| The next `major.minor` version |
79
+
|`NEXT_MINOR_VERSION_NO_PREFIX`| The next `major.minor` version without the tag prefix |
80
+
|`NEXT_MAJOR_VERSION`| The next `major` version |
81
+
|`NEXT_MAJOR_VERSION_NO_PREFIX`| The next `major` version without the tag prefix |
82
+
|`NEXT_VERSION_SHA`| The SHA of the next version as an environment variable |
83
+
|`PRIOR_VERSION`| The previous `major.minor.patch` version |
84
+
|`PRIOR_VERSION_NO_PREFIX`| The previous `major.minor.patch` version without the tag prefix |
85
+
|`NEXT_RELEASE_VERSION`| The next `major.minor.patch` release version. This version will not contain the branch when calculating a pre-release version. |
86
+
|`NEXT_RELEASE_VERSON_NO_PREFIX`| The next `major.minor.patch` version without the tag prefix. This version will not contain the branch when calculating a pre-release version. |
85
87
86
88
## Breaking Changes
87
89
@@ -116,7 +118,7 @@ jobs:
116
118
117
119
- id: get-version
118
120
# You may also reference just the major version.
119
-
uses: im-open/git-version-lite@v3.1.0
121
+
uses: im-open/git-version-lite@v3.2.0
120
122
with:
121
123
calculate-prerelease-version: true
122
124
branch-name: ${{ github.head_ref }} # github.head_ref works when the trigger is pull_request
@@ -145,7 +147,7 @@ When creating PRs, please review the following guidelines:
145
147
This repo uses [git-version-lite] in its workflows to examine commit messages to determine whether to perform a major, minor or patch increment on merge if [source code] changes have been made. The following table provides the fragment that should be included in a commit message to active different increment strategies.
Copy file name to clipboardExpand all lines: action.yml
+6Lines changed: 6 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -52,6 +52,12 @@ outputs:
52
52
PRIOR_VERSION_NO_PREFIX:
53
53
description: 'The previous major.minor.patch version without the tag prefix.'
54
54
55
+
NEXT_RELEASE_VERSION:
56
+
description: 'The calculated next release version. This version will not contain the branch when calculating a pre-release version.'
57
+
58
+
NEXT_RELEASE_VERSION_NO_PREFIX:
59
+
description: 'The calculated next release version without the tag prefix. This version will not contain the branch when calculating a pre-release version.'
0 commit comments