@ferrflow/doc 7.21.5 → 7.21.7
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/data/benchmarks.json +702 -702
- package/docs-en/reference/cli.md +1 -1
- package/docs-fr/reference/cli.md +1 -1
- package/package.json +1 -1
package/docs-en/reference/cli.md
CHANGED
|
@@ -190,7 +190,7 @@ ferrflow migrate # auto-detect
|
|
|
190
190
|
ferrflow migrate --from release-please
|
|
191
191
|
```
|
|
192
192
|
|
|
193
|
-
JSON, YAML, and JavaScript source configs all work
|
|
193
|
+
JSON, YAML, and JavaScript source configs all work. A JavaScript config (`.releaserc.js`, `.releaserc.cjs`, `.releaserc.mjs`, `release.config.js`, `release.config.cjs`, `release.config.mjs`, `.versionrc.js`) is run with `node` to read what it exports, so it needs Node.js on PATH. Being run is the point worth noticing: that file is a program, and migrating it executes it, along with anything it imports. semantic-release does the same, and there is no way to read an arbitrary module's exports without running it, so migrate only a repository you trust. `--dry-run` is no protection here: `migrate` ignores the flag, so the config runs and `ferrflow.json` is written either way. A YAML config (`.releaserc.yaml`, `.versionrc.yaml`) is parsed directly. After migrating, review the generated config, then run `ferrflow validate` and `ferrflow check`.
|
|
194
194
|
|
|
195
195
|
---
|
|
196
196
|
|
package/docs-fr/reference/cli.md
CHANGED
|
@@ -159,7 +159,7 @@ ferrflow migrate # auto-détection
|
|
|
159
159
|
ferrflow migrate --from release-please
|
|
160
160
|
```
|
|
161
161
|
|
|
162
|
-
Les configurations source JSON, YAML et JavaScript fonctionnent toutes. Une configuration JavaScript (`.releaserc.js`, `release.config.js`, `.versionrc.js`) est
|
|
162
|
+
Les configurations source JSON, YAML et JavaScript fonctionnent toutes. Une configuration JavaScript (`.releaserc.js`, `.releaserc.cjs`, `.releaserc.mjs`, `release.config.js`, `release.config.cjs`, `release.config.mjs`, `.versionrc.js`) est exécutée avec `node` pour lire ce qu'elle exporte, Node.js doit donc être dans le PATH. Le mot exécutée compte : ce fichier est un programme, et le migrer le lance, ainsi que tout ce qu'il importe. semantic-release fait la même chose, et il n'existe aucun moyen de lire les exports d'un module arbitraire sans le lancer : ne migrez donc qu'un dépôt de confiance. `--dry-run` ne protège pas : `migrate` ignore ce drapeau, la configuration est donc lancée et `ferrflow.json` écrit dans les deux cas. Une configuration YAML (`.releaserc.yaml`, `.versionrc.yaml`) est parsée directement. Après migration, relisez la configuration générée, puis lancez `ferrflow validate` et `ferrflow check`.
|
|
163
163
|
|
|
164
164
|
---
|
|
165
165
|
|