@ferrflow/darwin-x64 2.20.2 → 2.21.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 +16 -0
- package/bin/ferrflow +0 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -373,6 +373,22 @@ release_commit_mode = "pr"
|
|
|
373
373
|
auto_merge_releases = true # default
|
|
374
374
|
```
|
|
375
375
|
|
|
376
|
+
### Release Commit Scope
|
|
377
|
+
|
|
378
|
+
In monorepo mode, controls whether all package bumps go into a single commit or one commit per package:
|
|
379
|
+
|
|
380
|
+
```toml
|
|
381
|
+
[workspace]
|
|
382
|
+
release_commit_scope = "grouped" # default
|
|
383
|
+
```
|
|
384
|
+
|
|
385
|
+
| Scope | Description |
|
|
386
|
+
|-------|-------------|
|
|
387
|
+
| `grouped` | Single commit for all packages (e.g. `chore(release): api v1.0.0, site v2.1.0`) |
|
|
388
|
+
| `per-package` | One commit per package (e.g. `chore(release): api v1.0.0`, then `chore(release): site v2.1.0`) |
|
|
389
|
+
|
|
390
|
+
Per-package commits make it easier to revert a single package bump without affecting others. This works with both `commit` and `pr` release modes.
|
|
391
|
+
|
|
376
392
|
### Skip CI
|
|
377
393
|
|
|
378
394
|
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