Skip to content

Commit 5f2d2bc

Browse files
fix(ci): place --no-raise before bump subcommand
The bump-version step in bumpversion.yml passed --no-raise 21 after the `bump` subcommand, but `--no-raise` is a top-level commitizen option. With it placed after the subcommand, argparse treats `--no-raise 21` as unknown trailing arguments and the CLI exits with code 18 (`INVALID_COMMAND_ARGUMENT`): Invalid commitizen arguments were found: `--no-raise`. Please use -- separator for extra git args This is what failed the bump workflow on master in run 25542335831. Move the option before `bump` so it is parsed by the parent parser, as intended by 5513e01 (`ci(bump): gracefully handle no bump-eligible commits`). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
1 parent a656af5 commit 5f2d2bc

1 file changed

Lines changed: 3 additions & 1 deletion

File tree

.github/workflows/bumpversion.yml

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,9 @@ jobs:
3939
- id: bump-version
4040
run: |
4141
old_sha="$(git rev-parse HEAD)"
42-
cz bump --yes --no-raise 21
42+
# `--no-raise` is a top-level option, so it must come before the
43+
# `bump` subcommand. Exit code 21 is NO_COMMITS_TO_BUMP.
44+
cz --no-raise 21 bump --yes
4345
4446
if [ "$(git rev-parse HEAD)" = "$old_sha" ]; then
4547
echo "No bump-eligible commits found, skipping release."

0 commit comments

Comments
 (0)