@ferrflow/linux-arm 7.35.5 → 7.36.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 +17 -0
- package/bin/ferrflow +0 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -192,6 +192,8 @@ ferrflow migrate --from semantic-release
|
|
|
192
192
|
|
|
193
193
|
It maps `tagFormat`, `branches`, and the common plugins (`changelog`, `exec`, `github`/`gitlab`) to their FerrFlow equivalents, and prints a summary of what mapped, what was ignored, and what needs manual review. Anything without a FerrFlow equivalent is surfaced, never guessed. JSON `.releaserc` is supported today; YAML `.releaserc` and JS `release.config.js` are reported as unsupported rather than mis-parsed.
|
|
194
194
|
|
|
195
|
+
`ferrflow migrate --from release-please` also maps `extra-files` (`generic` markers to a `txt` selector, `toml` on `Cargo.toml` and `json` on `$.version` to their formats), `bump-minor-pre-major` and `bump-patch-for-minor-pre-major` to `preMajor` (`breaking: minor`, `feat: patch`), and writes `autoMergeReleases: false` since release-please never merges its release PR. Lockfile updates are enabled when a versioned manifest has one. Entries it cannot express are listed under "Review manually". Only non-default keys are written.
|
|
196
|
+
|
|
195
197
|
### JSON Schema
|
|
196
198
|
|
|
197
199
|
Add `$schema` to get autocompletion and validation in VS Code, WebStorm, and any JSON-aware editor:
|
|
@@ -391,6 +393,21 @@ versioning = "calver" # override: date-based
|
|
|
391
393
|
| `sequential` | `N` | `42` | Simple incrementing build number |
|
|
392
394
|
| `zerover` | `0.MINOR.PATCH` | `0.15.2` | Permanently unstable, never hits 1.0 |
|
|
393
395
|
|
|
396
|
+
### Pre-1.0 bump rules
|
|
397
|
+
|
|
398
|
+
By default a `semver` project jumps to `1.0.0` on its first breaking change. Set `preMajor` to stay in 0.x: while the current major is `0`, a breaking change bumps what `breaking` says and a `feat` bumps what `feat` says (`minor` or `patch`). `fix` is unchanged.
|
|
399
|
+
|
|
400
|
+
```toml
|
|
401
|
+
[workspace]
|
|
402
|
+
versioning = "semver"
|
|
403
|
+
|
|
404
|
+
[workspace.preMajor]
|
|
405
|
+
breaking = "minor"
|
|
406
|
+
feat = "patch"
|
|
407
|
+
```
|
|
408
|
+
|
|
409
|
+
From `0.5.0`: `feat!` gives `0.6.0`, `feat` and `fix` give `0.5.1`. This matches release-please's `bump-minor-pre-major` plus `bump-patch-for-minor-pre-major`. From `1.0.0` on it has no effect, and `ferrflow release --force-version 1.0.0` leaves 0.x. Packages can override it with their own `preMajor`. Unset keeps the standard rules.
|
|
410
|
+
|
|
394
411
|
## Tag Template
|
|
395
412
|
|
|
396
413
|
By default, FerrFlow tags single-repo releases as `v1.2.3` and monorepo releases as `api@v1.2.3`. Customize with `tag_template` at the workspace or package level using `{name}` and `{version}` placeholders.
|
package/bin/ferrflow
CHANGED
|
Binary file
|
package/package.json
CHANGED