@ferrflow/darwin-arm64 2.20.3 → 2.22.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -73,6 +73,10 @@ ferrflow release
73
73
  # Dry run
74
74
  ferrflow release --dry-run
75
75
 
76
+ # Force a specific version (skips commit analysis)
77
+ ferrflow release --force-version 2.0.0 # single repo
78
+ ferrflow release --force-version api@3.0.0 # monorepo
79
+
76
80
  # Pre-release
77
81
  ferrflow release --channel beta
78
82
 
@@ -373,6 +377,22 @@ release_commit_mode = "pr"
373
377
  auto_merge_releases = true # default
374
378
  ```
375
379
 
380
+ ### Release Commit Scope
381
+
382
+ In monorepo mode, controls whether all package bumps go into a single commit or one commit per package:
383
+
384
+ ```toml
385
+ [workspace]
386
+ release_commit_scope = "grouped" # default
387
+ ```
388
+
389
+ | Scope | Description |
390
+ |-------|-------------|
391
+ | `grouped` | Single commit for all packages (e.g. `chore(release): api v1.0.0, site v2.1.0`) |
392
+ | `per-package` | One commit per package (e.g. `chore(release): api v1.0.0`, then `chore(release): site v2.1.0`) |
393
+
394
+ Per-package commits make it easier to revert a single package bump without affecting others. This works with both `commit` and `pr` release modes.
395
+
376
396
  ### Skip CI
377
397
 
378
398
  By default, release commits in `commit` mode include `[skip ci]` in the message to avoid triggering a CI loop. Override with `skip_ci`:
package/bin/ferrflow CHANGED
Binary file
package/package.json CHANGED
@@ -12,5 +12,5 @@
12
12
  "type": "git",
13
13
  "url": "git+https://github.com/FerrFlow-Org/FerrFlow.git"
14
14
  },
15
- "version": "2.20.3"
15
+ "version": "2.22.0"
16
16
  }