@ferrflow/win32-arm64 7.35.6 → 7.36.0

package/README.md

@@ -192,6 +192,8 @@ ferrflow migrate --from semantic-release
 
 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.
 
+`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.
+
 ### JSON Schema
 
 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
 | `sequential` | `N` | `42` | Simple incrementing build number |
 | `zerover` | `0.MINOR.PATCH` | `0.15.2` | Permanently unstable, never hits 1.0 |
 
+### Pre-1.0 bump rules
+
+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.
+
+```toml
+[workspace]
+versioning = "semver"
+
+[workspace.preMajor]
+breaking = "minor"
+feat = "patch"
+```
+
+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.
+
 ## Tag Template
 
 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/package.json

@@ -12,5 +12,5 @@
     "type": "git",
     "url": "git+https://github.com/FerrLabs/FerrFlow.git"
   },
-  "version": "7.35.6"
+  "version": "7.36.0"
 }