@ferrflow/win32-arm64 5.31.4 → 5.32.1
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 +9 -0
- package/bin/ferrflow.exe +0 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -129,6 +129,15 @@ ferrflow init --format toml
|
|
|
129
129
|
ferrflow init --format dotfile # generates .ferrflow
|
|
130
130
|
```
|
|
131
131
|
|
|
132
|
+
Already using semantic-release? `ferrflow migrate` reads your existing config and generates the equivalent `ferrflow.json`:
|
|
133
|
+
|
|
134
|
+
```bash
|
|
135
|
+
ferrflow migrate # auto-detects .releaserc
|
|
136
|
+
ferrflow migrate --from semantic-release
|
|
137
|
+
```
|
|
138
|
+
|
|
139
|
+
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.
|
|
140
|
+
|
|
132
141
|
### JSON Schema
|
|
133
142
|
|
|
134
143
|
Add `$schema` to get autocompletion and validation in VS Code, WebStorm, and any JSON-aware editor:
|
package/bin/ferrflow.exe
CHANGED
|
Binary file
|
package/package.json
CHANGED