fix(release): cargo-workspaces 0.4.2 flag compatibility
cargo-workspaces 0.4.2 rejects `--no-git-commit` combined with `--no-git-tag`/`--no-git-push`/`--allow-branch`. With `--no-git-commit` no git operations run (so the default `--allow-branch master` check is skipped), making those flags both redundant and disallowed. Drop them so `make patch|minor|major|custom` works again. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
keypair34 committed
Jun 28, 2026 at 12:44 UTC
5f00617dc85b0cf697de17ab99e61a29db8082c9
1 file changed
+2
-2
Makefile
+2
-2
@@ -13,9 +13,9 @@ release:
13
@if [ "$$(git branch --show-current)" != "development" ]; then echo "Releases must be prepared on the development branch"; exit 1; fi
14
@if [ -n "$$(git status --short --untracked-files=all)" ]; then echo "Working tree must be clean before running a release"; exit 1; fi
15
@if [ "$(BUMP)" = "custom" ]; then \
16
- cargo workspaces version custom "$(VERSION)" --yes --no-git-commit --no-git-tag --no-git-push --allow-branch "*" --force "*"; \
16
+ cargo workspaces version custom "$(VERSION)" --yes --no-git-commit --force "*"; \
17
else \
18
- cargo workspaces version "$(BUMP)" --yes --no-git-commit --no-git-tag --no-git-push --allow-branch "*" --force "*"; \
18
+ cargo workspaces version "$(BUMP)" --yes --no-git-commit --force "*"; \
19
fi
20
@$(MAKE) sync-release-metadata
21
@$(MAKE) regenerate-release-lockfiles