|
49 | 49 | name: "Bump version and create changelog with commitizen" |
50 | 50 | steps: |
51 | 51 | - name: Check out |
52 | | - uses: actions/checkout@v3 |
| 52 | + uses: actions/checkout@v5 |
53 | 53 | with: |
54 | 54 | fetch-depth: 0 |
55 | 55 | token: "${{ secrets.GITHUB_TOKEN }}" |
|
80 | 80 | | `push` | Define if the changes should be pushed to the branch. | true | |
81 | 81 | | `merge` | Define if the changes should be pushed even on the pull_request event, immediately merging the pull request. | false | |
82 | 82 | | `commit` | Define if the changes should be committed to the branch. | true | |
83 | | -| `commitizen_version` | Specify the version to be used by commitizen. Eg: `2.21. | latest | |
| 83 | +| `commitizen_version` | Specify the version to be used by commitizen. Eg: `4.10.0` | latest | |
84 | 84 | | `changelog` | Create changelog when bumping the version | true | |
85 | 85 | | `no_raise` | Don't raise the given comma-delimited exit codes (e.g., no_raise: '20,21'). Use with caution! Open an issue in [commitizen](https://github.com/commitizen-tools/commitizen/issues) if you need help thinking about your workflow. | [21](https://commitizen-tools.github.io/commitizen/exit_codes/) | |
86 | 86 | | `increment` | Manually specify the desired increment {MAJOR,MINOR, PATCH} | - | |
|
90 | 90 |
|
91 | 91 | ## Outputs |
92 | 92 |
|
93 | | -| Name | Description | |
94 | | -| --------- | --------------- | |
95 | | -| `version` | The new version | |
| 93 | +| Name | Description | |
| 94 | +| ------------------------ | ----------------------------------------------------------------------- | |
| 95 | +| `version` | The next version (same as `next_version`, kept for historical purposes) | |
| 96 | +| `next_version` | Next version | |
| 97 | +| `next_version_major` | Only the major version of the next version | |
| 98 | +| `next_version_minor` | Only the minor version of the next version | |
| 99 | +| `previous_version` | Version before the bump | |
| 100 | +| `previous_version_major` | Only the major version of the previous version | |
| 101 | +| `previous_version_minor` | Only the minor version of the previous version | |
96 | 102 |
|
97 | 103 | The new version is also available as an environment variable under `REVISION` or you can access using `${{ steps.cz.outputs.version }}` |
98 | 104 |
|
@@ -176,6 +182,12 @@ To solve it, you must use a personal access token in the checkout and the commit |
176 | 182 |
|
177 | 183 | Follow the instructions in [commitizen's documentation][cz-docs-ga]. |
178 | 184 |
|
| 185 | +Alternatively, you can try using the `gh` cli in your github action: |
| 186 | + |
| 187 | +```sh |
| 188 | +gh workflow run <workflow.yaml> ... |
| 189 | +``` |
| 190 | + |
179 | 191 | ## I'm not using conventional commits, I'm using my own set of rules on commits |
180 | 192 |
|
181 | 193 | If your rules can be parsed, then you can build your own commitizen rules, |
|
0 commit comments