@ferrflow/doc 7.29.0 → 7.30.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/changelog/2026-04-24-ferrflow-changelog-ordering.md +11 -0
- package/changelog/2026-04-28-ferrflow-editorial-hero.md +11 -0
- package/changelog/2026-04-29-ferrflow-docs-claude-style.md +22 -0
- package/changelog/2026-04-29-ferrflow-editorial-body.md +16 -0
- package/changelog/2026-04-29-ferrflow-v4-2-prerelease-channels.md +27 -0
- package/changelog/2026-05-05-ferrflow-do-not-track-and-first-run-notice.md +22 -0
- package/changelog/2026-06-07-ferrflow-bot-release-rulesets.md +29 -0
- package/changelog/2026-06-16-ferrflow-declarative-publishers.md +40 -0
- package/changelog/2026-06-25-ferrflow-jobs-flag.md +24 -0
- package/changelog/2026-06-25-ferrflow-publish-tag-scope.md +35 -0
- package/changelog/2026-06-26-ferrflow-arm-targets.md +24 -0
- package/changelog/2026-07-13-ferrflow-hook-points.md +32 -0
- package/changelog/2026-07-16-ferrflow-migrate-semantic-release.md +41 -0
- package/changelog/2026-07-17-ferrflow-linked-fixed-groups.md +23 -0
- package/changelog/2026-07-17-ferrflow-telemetry-removed.md +14 -0
- package/changelog/2026-07-18-ferrflow-bitbucket.md +20 -0
- package/changelog/2026-07-18-ferrflow-breaking-change-variants.md +20 -0
- package/changelog/2026-07-18-ferrflow-commit-graph.md +14 -0
- package/changelog/2026-07-18-ferrflow-doctor.md +21 -0
- package/changelog/2026-07-18-ferrflow-schema-subcommand.md +19 -0
- package/changelog/2026-07-18-ferrflow-selfhosted-forge-autodetect.md +19 -0
- package/changelog/2026-07-20-ferrflow-hook-all-packages.md +32 -0
- package/changelog/2026-07-20-ferrflow-rich-hook-context.md +35 -0
- package/changelog/2026-07-21-ferrflow-diff-command.md +20 -0
- package/changelog/2026-07-21-ferrflow-hook-release-url.md +27 -0
- package/changelog/2026-07-21-ferrflow-hosted-api.md +26 -0
- package/changelog/2026-07-21-ferrflow-migrate-js-yaml.md +19 -0
- package/changelog/2026-07-21-ferrflow-migrate-more-tools.md +24 -0
- package/changelog/2026-07-21-ferrflow-persistent-release-pr.md +17 -0
- package/changelog/2026-07-25-ferrflow-concurrent-release-replan.md +14 -0
- package/changelog/2026-07-27-ferrflow-cabal-cmake-formats.md +23 -0
- package/changelog/2026-07-27-ferrflow-cosign-bundles.md +25 -0
- package/changelog/2026-07-27-ferrflow-tags-before-releases.md +14 -0
- package/changelog/2026-07-28-ferrflow-changesets-workspace-discovery.md +17 -0
- package/changelog/2026-08-04-ferrflow-diff-package-scope.md +21 -0
- package/changelog/2026-08-05-ferrflow-api-own-domain.md +25 -0
- package/changelog/2026-08-07-ferrflow-action-input-hardening.md +18 -0
- package/changelog/2026-08-07-ferrflow-mit-license.md +26 -0
- package/changelog/2026-08-07-ferrflow-verified-installs.md +28 -0
- package/changelog/2026-08-10-ferrflow-commit-formats.md +46 -0
- package/changelog/2026-08-15-ferrflow-lockfile-refresh.md +16 -0
- package/changelog/2026-08-20-ferrflow-version-source-option.md +29 -0
- package/changelog/2026-08-20-ferrflow-version-source.md +23 -0
- package/changelog/2026-08-25-ferrflow-bot-verified-commits.md +19 -0
- package/changelog/2026-08-25-ferrflow-config-include.md +30 -0
- package/changelog/2026-08-25-ferrflow-pr-mode-tags-on-merge.md +21 -0
- package/changelog/2026-08-25-ferrflow-push-error-classification.md +24 -0
- package/changelog/2026-08-27-ferrflow-rollback.md +27 -0
- package/changelog/2026-08-27-ferrflow-workspace-defaults.md +34 -0
- package/changelog/2026-08-28-ferrflow-annotated-tag-deref.md +26 -0
- package/changelog/2026-08-28-ferrflow-cache-staleness.md +19 -0
- package/changelog/2026-08-28-ferrflow-cargo-publish-url.md +28 -0
- package/changelog/2026-08-28-ferrflow-npm-publish-url.md +27 -0
- package/changelog/2026-08-28-ferrflow-panic-cleanup.md +19 -0
- package/changelog/2026-08-29-ferrflow-calver-short-seq.md +31 -0
- package/changelog/2026-08-29-ferrflow-scoped-package-commits.md +23 -0
- package/changelog/2026-09-01-ferrflow-cascade-strongest-bump.md +25 -0
- package/changelog/2026-09-01-ferrflow-changelog-hook-rewrite.md +21 -0
- package/changelog/2026-09-01-ferrflow-doctor-lockfile.md +36 -0
- package/changelog/2026-09-01-ferrflow-graph-impact.md +34 -0
- package/changelog/2026-09-01-ferrflow-own-bump-raised.md +25 -0
- package/changelog/2026-09-02-ferrflow-galaxyyml.md +25 -0
- package/changelog/2026-09-03-ferrflow-docs-public.md +17 -0
- package/changelog/2026-09-04-ferrflow-build-metadata.md +27 -0
- package/changelog/2026-09-22-ferrflow-package-schema.md +31 -0
- package/changelog/2026-09-22-ferrflow-push-token-per-forge.md +23 -0
- package/changelog/2026-09-22-ferrflow-release-git-identity.md +18 -0
- package/changelog/2026-09-23-ferrflow-release-mr-title-length.md +21 -0
- package/changelog/2026-09-24-ferrflow-selector-padding.md +19 -0
- package/changelog/2026-09-24-ferrflow-template-leading-v.md +19 -0
- package/changelog/2026-09-24-ferrflow-template-literals.md +21 -0
- package/changelog/2026-09-28-ferrflow-floating-tag-backward.md +12 -0
- package/changelog/2026-09-28-ferrflow-helm-chart-name.md +12 -0
- package/changelog/2026-09-28-ferrflow-migrate-tag-template.md +23 -0
- package/changelog/2026-09-28-ferrflow-padded-versions.md +12 -0
- package/changelog/2026-10-02-ferrflow-shadow-release.md +17 -0
- package/changelog/2026-10-03-ferrflow-latest-tag-hotfix.md +13 -0
- package/changelog/2026-10-03-ferrflow-pr-lookup-branch-encoding.md +12 -0
- package/changelog/2026-10-03-ferrflow-preview-backtick.md +12 -0
- package/changelog/2026-10-03-ferrflow-why-doctor-wording.md +10 -0
- package/changelog/2026-10-07-ferrflow-strategy-names-json.md +12 -0
- package/changelog/2026-10-10-ferrflow-hook-timeout.md +23 -0
- package/changelog/2026-10-10-ferrflow-init-workspace-discovery.md +16 -0
- package/data/benchmarks.json +683 -683
- package/docs-en/reference/cli.md +2 -0
- package/docs-fr/reference/cli.md +2 -0
- package/package.json +1 -1
|
@@ -0,0 +1,11 @@
|
|
|
1
|
+
---
|
|
2
|
+
title: 'FerrFlow: changelog ordering fix'
|
|
3
|
+
summary: 'Changelog entries are now sorted by commit date instead of alphabetically inside each section.'
|
|
4
|
+
date: 2026-04-24T11:15:00Z
|
|
5
|
+
product: 'ferrflow'
|
|
6
|
+
type: 'fix'
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
Changelog entries were sorted alphabetically inside each section instead of by commit date. They are now grouped by date descending, which matches what every other release tool does and what humans actually expect.
|
|
10
|
+
|
|
11
|
+
Affects everyone running v4.x. Re-run `ferrflow changelog` to regenerate the file with the corrected ordering.
|
|
@@ -0,0 +1,11 @@
|
|
|
1
|
+
---
|
|
2
|
+
title: 'FerrFlow: editorial hero on the landing page'
|
|
3
|
+
summary: 'New display headline (Fraunces 900, italic accent), softer paper background, monospace eyebrows.'
|
|
4
|
+
date: 2026-04-28T20:59:00Z
|
|
5
|
+
product: 'ferrflow'
|
|
6
|
+
type: 'new'
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
The FerrFlow landing page now leads with an editorial hero: large display headline in Fraunces, italic accent line, monospace eyebrow markers. First step of the FerrLabs design system rollout for ferrflow.com.
|
|
10
|
+
|
|
11
|
+
Same content, more confident voice. Nothing changed in the CLI itself.
|
|
@@ -0,0 +1,22 @@
|
|
|
1
|
+
---
|
|
2
|
+
title: 'FerrFlow: docs in the Claude style'
|
|
3
|
+
summary: 'ferrflow.com/docs/ adopts the visual language of docs.claude.com: off-white background, FerrFlow orange accent, soft-dark code blocks, accent-bar callouts, a 3-column layout and <Card>/<CardGroup>/<Note> components.'
|
|
4
|
+
date: 2026-04-29T16:30:00Z
|
|
5
|
+
product: 'ferrflow'
|
|
6
|
+
type: 'new'
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
The default Starlight docs did their job but looked generic. They now borrow the visual language of the Anthropic docs, keeping FerrFlow orange as the single accent instead of Anthropic's clay.
|
|
10
|
+
|
|
11
|
+
What changes visually:
|
|
12
|
+
|
|
13
|
+
- **Off-white `#fafafa` background** (light) and **near-black `#0a0a0a`** (dark), with zinc text.
|
|
14
|
+
- **Inter system stack** for body text, Fraunces kept for headings.
|
|
15
|
+
- **FerrFlow orange accent `#e8733a`** (light) and `#ef8a55` (dark) for links, focus rings and the active sidebar item.
|
|
16
|
+
- **Soft-dark code blocks `#1c1c1c`** even in light mode, 12px rounded, language label top-left, copy button top-right on hover.
|
|
17
|
+
- **Tinted-card callouts** with a 4px accent bar on the left: `<Note>`, `<Tip>`, `<Warning>`, `<Info>`.
|
|
18
|
+
- **Mintlify-style components** `<Card>` and `<CardGroup cols={2|3}>` for value grids.
|
|
19
|
+
- **Small-caps breadcrumb** "Section › Page" above the H1.
|
|
20
|
+
- **"Was this page helpful?" widget** and an "Edit on GitHub" link at the bottom of every page.
|
|
21
|
+
|
|
22
|
+
Layout, version and language sidebar, ExpressiveCode, FR translations and the `v0`/`v1`/`v2`/`v3` snapshots inherit it automatically since the CSS is global. Pagefind search is unchanged. The Cmd+K modal keeps its Starlight style for now.
|
|
@@ -0,0 +1,16 @@
|
|
|
1
|
+
---
|
|
2
|
+
title: 'FerrFlow: editorial features grid, install grid, dark CTA'
|
|
3
|
+
summary: 'The body of ferrflow.com now matches the new editorial design: six feature cards in a single bordered grid, four install methods side by side, dark contrast CTA block.'
|
|
4
|
+
date: 2026-04-29T11:23:00Z
|
|
5
|
+
product: 'ferrflow'
|
|
6
|
+
type: 'new'
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
The ferrflow.com landing page is now fully on the editorial design system, end to end. The hero refresh shipped a few days ago; this one finishes the body:
|
|
10
|
+
|
|
11
|
+
- **Stats strip**: hairline row listing the 13 file formats FerrFlow reads natively (Cargo.toml, package.json, pyproject.toml, pom.xml, *.csproj, build.gradle, Chart.yaml, pubspec.yaml, mix.exs, *.gemspec, Package.swift, go.mod, composer.json).
|
|
12
|
+
- **Features section**: `№ 02` numbered, six feature cards in a single bordered container with hairline dividers. No more colored icon boxes.
|
|
13
|
+
- **Install section**: `№ 03`, four install methods side by side (Cargo / npm / Docker / GitHub Action), each with a mono `$` prompt in accent orange.
|
|
14
|
+
- **CTA block**: `№ 04`, dark contrast block with an 8px orange border-left, big Fraunces title with italic accent, two pill CTAs.
|
|
15
|
+
|
|
16
|
+
Old terminal mock and 5-feature icon grid removed.
|
|
@@ -0,0 +1,27 @@
|
|
|
1
|
+
---
|
|
2
|
+
title: 'FerrFlow v4.2: pre-release channels'
|
|
3
|
+
summary: 'Ship `alpha`, `beta`, and `rc` releases without touching your floating tags.'
|
|
4
|
+
date: 2026-04-29T09:00:00Z
|
|
5
|
+
product: 'ferrflow'
|
|
6
|
+
type: 'new'
|
|
7
|
+
docsLink: 'https://ferrflow.com/docs/guides/prerelease-channels'
|
|
8
|
+
---
|
|
9
|
+
|
|
10
|
+
You can now ship `alpha`, `beta`, and `rc` releases without touching your floating tags. Add `--prerelease=beta` to the CLI or set `prerelease.channel` in `.ferrflow` and FerrFlow will tag `v4.2.0-beta.1`, `v4.2.0-beta.2` and so on without bumping `latest`.
|
|
11
|
+
|
|
12
|
+
```bash
|
|
13
|
+
ferrflow release --prerelease=beta
|
|
14
|
+
```
|
|
15
|
+
|
|
16
|
+
## Why we built it
|
|
17
|
+
|
|
18
|
+
Three teams asked for it last quarter. Every one of them was using a hacky `--no-publish` workaround. This fixes the workaround.
|
|
19
|
+
|
|
20
|
+
## What changes
|
|
21
|
+
|
|
22
|
+
- New `prerelease.channel` config field (string, no default).
|
|
23
|
+
- New `--prerelease=<channel>` CLI flag (overrides config).
|
|
24
|
+
- Floating tags (`latest`, `next`) stay pinned to non-prerelease versions.
|
|
25
|
+
- Generated changelogs include a `Pre-releases` section under each major.
|
|
26
|
+
|
|
27
|
+
No breaking changes. Existing repos get the feature for free on next bump to `v4.2.0`.
|
|
@@ -0,0 +1,22 @@
|
|
|
1
|
+
---
|
|
2
|
+
title: 'FerrFlow: DO_NOT_TRACK env var + first-run telemetry notice'
|
|
3
|
+
summary: 'Telemetry now honours DO_NOT_TRACK=1 alongside FERRFLOW_TELEMETRY=0, and the first invocation prints a one-line notice pointing to ferrlabs.com/telemetry.'
|
|
4
|
+
date: 2026-05-05T19:30:00Z
|
|
5
|
+
product: ferrflow
|
|
6
|
+
type: new
|
|
7
|
+
docsLink: https://ferrlabs.com/telemetry
|
|
8
|
+
---
|
|
9
|
+
|
|
10
|
+
Two small additions to make the FerrFlow CLI's anonymous telemetry friendlier and more discoverable.
|
|
11
|
+
|
|
12
|
+
**`DO_NOT_TRACK=1`** now disables anonymous telemetry, exactly like `FERRFLOW_TELEMETRY=0`. Same precedence: `DO_NOT_TRACK` wins if set to `1`/`true`/`yes`/`on`. Adopting the [Console Do Not Track](https://consoledonottrack.com/) standard means a single env var in your shell profile turns off telemetry for FerrFlow, Bun, Astro, Next.js, Vite, Deno and the rest of the dev tools that honour it. No need to learn one variable per CLI.
|
|
13
|
+
|
|
14
|
+
**First-run notice.** The first time you run the CLI on a machine, it prints one line to stderr:
|
|
15
|
+
|
|
16
|
+
```
|
|
17
|
+
Anonymous telemetry on. See https://ferrlabs.com/telemetry — opt out: FERRFLOW_TELEMETRY=0 or DO_NOT_TRACK=1
|
|
18
|
+
```
|
|
19
|
+
|
|
20
|
+
A marker file in `$XDG_STATE_HOME/ferrflow/.telemetry-notice-shown` (or `~/Library/Application Support/ferrflow/` on macOS, `%LOCALAPPDATA%\ferrflow\` on Windows, override with `FERRFLOW_STATE_DIR`) suppresses it on subsequent runs. We never silently re-enable telemetry between versions; if you opted out, the notice doesn't print and nothing is sent.
|
|
21
|
+
|
|
22
|
+
Part of [FerrLabs-Cloud#166](https://github.com/FerrLabs/FerrLabs-Cloud/issues/166).
|
|
@@ -0,0 +1,29 @@
|
|
|
1
|
+
---
|
|
2
|
+
title: 'FerrFlow: bot releases now work under branch rulesets (v5.2.2)'
|
|
3
|
+
summary: The FerrFlow bot identity pushes releases correctly even when the release branch is protected by a ruleset that bypasses ferrflow[bot]. Shipped in FerrFlow v5.2.2.
|
|
4
|
+
date: 2026-06-07T11:00:00Z
|
|
5
|
+
product: ferrflow
|
|
6
|
+
type: fix
|
|
7
|
+
prLink: https://github.com/FerrLabs/FerrFlow/pull/539
|
|
8
|
+
---
|
|
9
|
+
|
|
10
|
+
Releases run with `bot: true` now push correctly even when your release branch is protected by a GitHub ruleset that bypasses `ferrflow[bot]`. Before this fix, the release commit could be rejected with `GH013: required status checks are expected` even though `ferrflow[bot]` was listed as a bypass actor. Shipped in **FerrFlow v5.2.2**: pinning the major (`FerrLabs/FerrFlow@v5`) picks it up automatically.
|
|
11
|
+
|
|
12
|
+
### Why it happened
|
|
13
|
+
|
|
14
|
+
`actions/checkout` persists your workflow's `GITHUB_TOKEN` as an `http.<server>.extraheader` git config entry. An HTTP extra-header outranks a credential helper, so even though FerrFlow swaps in its OIDC-minted bot token, git kept sending the original `GITHUB_TOKEN` on every push. The release commit therefore landed as `github-actions[bot]`, which is not a bypass actor, and the ruleset rejected it.
|
|
15
|
+
|
|
16
|
+
### What changes
|
|
17
|
+
|
|
18
|
+
FerrFlow now resets that persisted extra-header on its own git invocations, so its bot token is the only credential on the wire and the push lands as `ferrflow[bot]`. This works regardless of your `actions/checkout` version and no longer requires `persist-credentials: false` on the checkout step.
|
|
19
|
+
|
|
20
|
+
```yaml
|
|
21
|
+
- uses: actions/checkout@v6
|
|
22
|
+
with:
|
|
23
|
+
fetch-depth: 0
|
|
24
|
+
- uses: FerrLabs/FerrFlow@v5
|
|
25
|
+
with:
|
|
26
|
+
bot: true
|
|
27
|
+
```
|
|
28
|
+
|
|
29
|
+
No config changes needed: upgrade to `@v5` (or pin `@v5.2.2` explicitly) and protected release branches just work.
|
|
@@ -0,0 +1,40 @@
|
|
|
1
|
+
---
|
|
2
|
+
title: 'FerrFlow: declarative publishers (publish to cargo, npm, docker, helm & more on release)'
|
|
3
|
+
summary: 'FerrFlow can now publish your packages to registries declaratively from ferrflow.json (cargo, npm, docker with multi-arch + Sigstore, helm, GitHub release assets and webhooks), replacing hand-rolled postPublish shell hooks. Shipped across FerrFlow v5.4 to v5.7.'
|
|
4
|
+
date: 2026-06-16T10:00:00Z
|
|
5
|
+
product: ferrflow
|
|
6
|
+
type: new
|
|
7
|
+
docsLink: https://ferrflow.com/docs/configuration/config-file/#publishers
|
|
8
|
+
---
|
|
9
|
+
|
|
10
|
+
FerrFlow now publishes your packages to registries declaratively. Instead of wiring a `postPublish` shell hook that shells out to `cargo publish`, `npm publish`, or `docker buildx`, you describe the intent in `ferrflow.json` and FerrFlow runs it after the GitHub Release is created: per package, idempotently, and crash-resume safe.
|
|
11
|
+
|
|
12
|
+
Six publisher kinds are supported:
|
|
13
|
+
|
|
14
|
+
- **cargo**: `cargo publish` to crates.io or a private registry, with `allowDirty` and `noVerify`.
|
|
15
|
+
- **npm**: `npm publish` with a scoped, throwaway `.npmrc` so your project's `.npmrc` is never touched.
|
|
16
|
+
- **docker**: `docker buildx build --push` with multi-arch (`{version}`/`{major}`/`{minor}`/`latest` tag templates), and optional `sign: sigstore` (`cosign`).
|
|
17
|
+
- **helm**: `helm package` + `helm push` to an OCI registry.
|
|
18
|
+
- **github-release-asset**: attach a sidecar file (SBOM, signature, …) to the release with `--clobber`.
|
|
19
|
+
- **webhook**: POST to Slack/Discord/your own endpoint with `{name}`, `{version}`, `{tag}` and `{env:NAME}` interpolation.
|
|
20
|
+
|
|
21
|
+
```json title="ferrflow.json"
|
|
22
|
+
{
|
|
23
|
+
"workspace": {
|
|
24
|
+
"registries": {
|
|
25
|
+
"kellnr": { "tokenEnv": "CARGO_REGISTRIES_KELLNR_TOKEN" }
|
|
26
|
+
}
|
|
27
|
+
},
|
|
28
|
+
"package": [{
|
|
29
|
+
"name": "my-crate",
|
|
30
|
+
"path": "crates/my-crate",
|
|
31
|
+
"publishers": [
|
|
32
|
+
{ "kind": "cargo", "registry": "kellnr", "noVerify": true }
|
|
33
|
+
]
|
|
34
|
+
}]
|
|
35
|
+
}
|
|
36
|
+
```
|
|
37
|
+
|
|
38
|
+
Registry tokens are referenced by env-var name (`tokenEnv`): the token value never lives in the config file, so `ferrflow.json` stays safe to commit. Every command publisher also takes an `args` array, a verbatim escape hatch for flags FerrFlow doesn't model natively (`--locked`, `--provenance`, `--build-arg`, …).
|
|
39
|
+
|
|
40
|
+
Publishers are idempotent: an already-published version is detected and skipped, so a re-run after a partial failure picks up exactly where it left off. The block is additive: your existing `postPublish` hooks keep working while you migrate. See the [publishers documentation](https://ferrflow.com/docs/configuration/config-file/#publishers) for the full reference.
|
|
@@ -0,0 +1,24 @@
|
|
|
1
|
+
---
|
|
2
|
+
title: 'FerrFlow: control parallelism with --jobs / FERRFLOW_JOBS'
|
|
3
|
+
summary: 'FerrFlow now exposes a global --jobs <N> flag (and FERRFLOW_JOBS env var) to cap how many threads it uses for CPU-parallel work. Default stays all logical cores; --jobs 1 forces single-threaded: handy for constrained CI runners and reproducible benchmarks.'
|
|
4
|
+
date: 2026-06-25T10:00:00Z
|
|
5
|
+
product: ferrflow
|
|
6
|
+
type: new
|
|
7
|
+
prLink: https://github.com/FerrLabs/FerrFlow/pull/598
|
|
8
|
+
docsLink: https://ferrflow.com/docs/reference/cli/#global-flags
|
|
9
|
+
---
|
|
10
|
+
|
|
11
|
+
Since FerrFlow started planning packages and creating releases in parallel, two needs emerged: capping CPU use on small CI runners, and keeping benchmark numbers reproducible regardless of a machine's core count. The new global `--jobs <N>` flag (or the `FERRFLOW_JOBS` env var, with the flag taking precedence) covers both.
|
|
12
|
+
|
|
13
|
+
- **Default (unset):** all logical cores, exactly as before.
|
|
14
|
+
- **`--jobs N`:** caps per-package planning to N threads, and bounds the release-creation HTTP pool by N too, so `--jobs 1` makes the whole run single-threaded.
|
|
15
|
+
|
|
16
|
+
```bash
|
|
17
|
+
# Pin to one thread: deterministic, light on a 2-core runner
|
|
18
|
+
ferrflow --jobs 1 release
|
|
19
|
+
|
|
20
|
+
# Or via the environment
|
|
21
|
+
FERRFLOW_JOBS=4 ferrflow release
|
|
22
|
+
```
|
|
23
|
+
|
|
24
|
+
It works with every command, since it's a global flag.
|
|
@@ -0,0 +1,35 @@
|
|
|
1
|
+
---
|
|
2
|
+
title: 'FerrFlow: ferrflow publish auto-scopes to the triggering tag'
|
|
3
|
+
summary: 'ferrflow publish now figures out which package to publish from the tag that triggered the run, so one workflow publishes each package on its own tag, no per-package wiring. It also takes multiple package names, and a --all flag to force everything.'
|
|
4
|
+
date: 2026-06-25T11:00:00Z
|
|
5
|
+
product: ferrflow
|
|
6
|
+
type: new
|
|
7
|
+
prLink: https://github.com/FerrLabs/FerrFlow/pull/602
|
|
8
|
+
docsLink: https://ferrflow.com/docs/reference/cli/#ferrflow-publish
|
|
9
|
+
---
|
|
10
|
+
|
|
11
|
+
`ferrflow publish` runs your declarative publishers in a separate CI job. Until now it published one named package or all of them, which meant a tag-triggered job had to parse `api@v2.2.1` and pass `api` itself. No more: `ferrflow publish` reads the triggering tag (`GITHUB_REF` / `CI_COMMIT_TAG`) and publishes just that package.
|
|
12
|
+
|
|
13
|
+
So a single workflow handles a whole monorepo. Every package publishes on its own tag, with zero per-package wiring:
|
|
14
|
+
|
|
15
|
+
```yaml title=".github/workflows/publish.yml"
|
|
16
|
+
on:
|
|
17
|
+
push:
|
|
18
|
+
tags: ['v*', '*@v*'] # single-repo and monorepo per-package tags
|
|
19
|
+
jobs:
|
|
20
|
+
publish:
|
|
21
|
+
runs-on: ubuntu-latest
|
|
22
|
+
steps:
|
|
23
|
+
- uses: actions/checkout@v6
|
|
24
|
+
- uses: FerrLabs/FerrFlow@v5
|
|
25
|
+
with:
|
|
26
|
+
mode: publish # self-scopes to the tag that fired
|
|
27
|
+
```
|
|
28
|
+
|
|
29
|
+
The selection rules:
|
|
30
|
+
|
|
31
|
+
- **`ferrflow publish`**: triggering tag → that package; otherwise every package (unchanged, so the existing release→publish job is unaffected).
|
|
32
|
+
- **`ferrflow publish api web`**: explicit packages (now more than one).
|
|
33
|
+
- **`ferrflow publish --all`**: every package, ignoring any tag scope.
|
|
34
|
+
|
|
35
|
+
Scope is by package name / tag, not conventional-commit scope, and the version is still read from package state: the tag's version suffix is just informational.
|
|
@@ -0,0 +1,24 @@
|
|
|
1
|
+
---
|
|
2
|
+
title: 'FerrFlow: Windows arm64 and Linux armv7 prebuilt binaries'
|
|
3
|
+
summary: 'FerrFlow now ships prebuilt, signed binaries (and matching npm packages) for Windows on ARM (aarch64) and 32-bit ARM Linux (armv7). The release matrix grows from 5 targets to 7, so `npm i ferrflow` and direct downloads now work on Surface/Snapdragon Windows laptops and 32-bit Raspberry Pi / SBCs.'
|
|
4
|
+
date: 2026-06-26T10:00:00Z
|
|
5
|
+
product: ferrflow
|
|
6
|
+
type: new
|
|
7
|
+
prLink: https://github.com/FerrLabs/FerrFlow/pull/607
|
|
8
|
+
docsLink: https://ferrflow.com/docs/verifying-releases/
|
|
9
|
+
---
|
|
10
|
+
|
|
11
|
+
ARM64 was already covered on Linux and macOS, but not Windows, and 32-bit ARM Linux had no build at all. This release closes both gaps, taking the target matrix to seven.
|
|
12
|
+
|
|
13
|
+
Two new targets ship with every release, signed with Sigstore and listed in the SBOM exactly like the existing five:
|
|
14
|
+
|
|
15
|
+
- **`aarch64-pc-windows-msvc`** → `ferrflow-windows-arm64.zip` / `@ferrflow/win32-arm64`: Windows on ARM (Surface Pro X/11, Snapdragon X laptops, Dev Kit 2023).
|
|
16
|
+
- **`armv7-unknown-linux-musleabihf`** → `ferrflow-linux-armv7.tar.gz` / `@ferrflow/linux-arm`: 32-bit ARM Linux (Raspberry Pi on a 32-bit OS, older SBCs).
|
|
17
|
+
|
|
18
|
+
The npm wrapper resolves the right binary automatically through `optionalDependencies`, so nothing changes in how you install:
|
|
19
|
+
|
|
20
|
+
```bash
|
|
21
|
+
npm install -D ferrflow
|
|
22
|
+
```
|
|
23
|
+
|
|
24
|
+
On a Windows-on-ARM or armv7 machine npm now pulls the native package instead of failing. Prebuilt archives are also on the [GitHub release page](https://github.com/FerrLabs/FerrFlow/releases), and the GitHub Action installs the matching binary for the runner's architecture.
|
|
@@ -0,0 +1,32 @@
|
|
|
1
|
+
---
|
|
2
|
+
title: 'FerrFlow: Six new release hook points: post-commit, pre-tag, post-tag, pre-release, on-success, on-error'
|
|
3
|
+
summary: 'The release lifecycle gains six new hook points so you can run commands at the exact commit/tag/push boundaries: publish between tag and push, notify once when a release finishes, or react to a failure with the error code in hand.'
|
|
4
|
+
date: 2026-07-13T09:00:00Z
|
|
5
|
+
product: ferrflow
|
|
6
|
+
type: new
|
|
7
|
+
prLink: https://github.com/FerrLabs/FerrFlow/pull/657
|
|
8
|
+
docsLink: https://ferrflow.com/docs/configuration/config-file#hooks
|
|
9
|
+
---
|
|
10
|
+
|
|
11
|
+
FerrFlow already ran shell hooks at `pre_bump`, `post_bump`, `pre_commit`, `pre_publish`, and `post_publish`. That left gaps around the most delicate part of a release: the commit, the tag, and the push. This release fills them.
|
|
12
|
+
|
|
13
|
+
- **`post_commit`**: after the release commit, before tagging.
|
|
14
|
+
- **`pre_tag`**: after the commit, immediately before `git tag`. Smoke-test the bumped tree before the tag lands.
|
|
15
|
+
- **`post_tag`**: after tags are created, before push. This is the natural place to `cargo publish`: the tag exists locally but isn't pushed yet, so a failed publish is recoverable by dropping the local tag instead of rewriting remote history.
|
|
16
|
+
- **`pre_release`**: after the release pull request opens, before merge (`releaseCommitMode: pr` only). Post a review ping or run cross-repo validation.
|
|
17
|
+
- **`on_success`**: once, after the whole release finishes cleanly. Trigger a downstream deploy.
|
|
18
|
+
- **`on_error`**: once, when a release fails. It receives the failing error code in `FERRFLOW_ERROR_CODE`, so a Slack alert can link straight to the error reference.
|
|
19
|
+
|
|
20
|
+
```json
|
|
21
|
+
{
|
|
22
|
+
"workspace": {
|
|
23
|
+
"hooks": {
|
|
24
|
+
"postTag": "cargo publish",
|
|
25
|
+
"onSuccess": "curl -X POST $DEPLOY_WEBHOOK",
|
|
26
|
+
"onError": "curl -X POST $SLACK_WEBHOOK -d \"release failed: $FERRFLOW_ERROR_CODE\""
|
|
27
|
+
}
|
|
28
|
+
}
|
|
29
|
+
}
|
|
30
|
+
```
|
|
31
|
+
|
|
32
|
+
Per-package hooks (`post_commit`, `pre_tag`, `post_tag`) run once per released package; the once-per-run hooks (`pre_release`, `on_success`, `on_error`) fire a single time for the whole invocation. Note that `on_error` (the reactive hook) is distinct from `on_failure`, which stays what it always was: the `abort` / `continue` strategy for how a failing hook is handled.
|
|
@@ -0,0 +1,41 @@
|
|
|
1
|
+
---
|
|
2
|
+
title: 'FerrFlow: Migrate from semantic-release in one command'
|
|
3
|
+
summary: 'A new `ferrflow migrate` command reads your existing `.releaserc` and generates the equivalent FerrFlow config, mapping tag format, branches, and the common plugins, and surfacing anything without an equivalent instead of guessing.'
|
|
4
|
+
date: 2026-07-16T09:00:00Z
|
|
5
|
+
product: ferrflow
|
|
6
|
+
type: new
|
|
7
|
+
prLink: https://github.com/FerrLabs/FerrFlow/pull/699
|
|
8
|
+
docsLink: https://ferrflow.com/docs/reference/cli#ferrflow-migrate
|
|
9
|
+
---
|
|
10
|
+
|
|
11
|
+
Switching release tools shouldn't mean rewriting your config by hand. `ferrflow migrate` reads an existing semantic-release setup and writes the equivalent `ferrflow.json` for you.
|
|
12
|
+
|
|
13
|
+
```bash
|
|
14
|
+
ferrflow migrate # auto-detects .releaserc
|
|
15
|
+
ferrflow migrate --from semantic-release
|
|
16
|
+
```
|
|
17
|
+
|
|
18
|
+
It maps what has a FerrFlow equivalent:
|
|
19
|
+
|
|
20
|
+
- `tagFormat: "v${version}"` → `tagTemplate: "v{version}"`
|
|
21
|
+
- `branches` → FerrFlow channels: `main`/`master` become the stable line, a `prerelease` branch becomes a channel
|
|
22
|
+
- `@semantic-release/changelog` → the package's `changelog` path
|
|
23
|
+
- `@semantic-release/exec` → hooks (`prepareCmd` → `preBump`, `publishCmd` → `postPublish`, and the rest)
|
|
24
|
+
- `@semantic-release/github` / `gitlab` → `forge`
|
|
25
|
+
|
|
26
|
+
The point is what it does with the rest. Anything without a FerrFlow equivalent is **surfaced, never guessed**: `@semantic-release/npm`, custom `commit-analyzer` release rules, and `repositoryUrl` are each reported with a note on what to do, not silently dropped. The command prints a summary of what mapped, what it ignored, and what needs a manual look, and it won't overwrite a config you already have.
|
|
27
|
+
|
|
28
|
+
```
|
|
29
|
+
Migrated semantic-release config from .releaserc → ferrflow.json
|
|
30
|
+
|
|
31
|
+
Mapped:
|
|
32
|
+
• tagFormat → tagTemplate (v${version})
|
|
33
|
+
• branch main → stable
|
|
34
|
+
• branch beta → prerelease `beta`
|
|
35
|
+
• @semantic-release/github → forge
|
|
36
|
+
|
|
37
|
+
Review manually:
|
|
38
|
+
! @semantic-release/npm → not mapped. Configure `publishers` by hand if you publish to npm.
|
|
39
|
+
```
|
|
40
|
+
|
|
41
|
+
JSON `.releaserc` is supported today; a YAML `.releaserc` or a JavaScript `release.config.js` is reported as unsupported rather than mis-read. After migrating, review the generated config, then run `ferrflow validate` and `ferrflow check`.
|
|
@@ -0,0 +1,23 @@
|
|
|
1
|
+
---
|
|
2
|
+
title: 'FerrFlow: Linked and fixed package version groups'
|
|
3
|
+
summary: 'New `linked` and `fixed` workspace options let a set of monorepo packages share a version: when one bumps, the whole group moves to the same version, the way changesets and lerna do it.'
|
|
4
|
+
date: 2026-07-17T09:00:00Z
|
|
5
|
+
product: ferrflow
|
|
6
|
+
type: new
|
|
7
|
+
prLink: https://github.com/FerrLabs/FerrFlow/pull/724
|
|
8
|
+
docsLink: https://ferrflow.com/docs/configuration/monorepo#linked-and-fixed-version-groups
|
|
9
|
+
---
|
|
10
|
+
|
|
11
|
+
Until now the only way to couple packages in a monorepo was `dependsOn`, which cascades a bump but leaves each package on its own version. Some packages, though, are meant to move as one: `react` and `react-dom`, or a set of packages you publish under a single version line. `linked` and `fixed` express exactly that.
|
|
12
|
+
|
|
13
|
+
```toml
|
|
14
|
+
[workspace]
|
|
15
|
+
linked = [["react", "react-dom"]]
|
|
16
|
+
fixed = [["@scope/a", "@scope/b", "@scope/c"]]
|
|
17
|
+
```
|
|
18
|
+
|
|
19
|
+
When any member of a group has a releasable commit, every member is bumped to the same version: the highest the group would reach. A `feat` on one package and a `fix` on another release the whole group on the minor, and a member with no commits of its own is pulled in at the shared version. Package names stay distinct; only the number is shared.
|
|
20
|
+
|
|
21
|
+
`linked` packages share a version line when they're released together. `fixed` packages are locked to an identical version forever: the same behaviour, plus `ferrflow validate` warns if their versions have drifted apart so you catch a stray manual edit before the next release realigns them.
|
|
22
|
+
|
|
23
|
+
Misconfigurations are caught before anything is written: a group with a package that isn't defined, a package listed in two groups, or a group with fewer than two members stops the release with a clear error: the same pre-flight guarantee as dependency-cycle detection.
|
|
@@ -0,0 +1,14 @@
|
|
|
1
|
+
---
|
|
2
|
+
title: 'FerrFlow: Telemetry removed. The CLI no longer phones home'
|
|
3
|
+
summary: 'FerrFlow no longer collects any usage telemetry. The module is gone from the binary entirely, along with the network calls it made on every command, which also makes monorepo commands dramatically faster.'
|
|
4
|
+
date: 2026-07-17T15:00:00Z
|
|
5
|
+
product: ferrflow
|
|
6
|
+
type: new
|
|
7
|
+
prLink: https://github.com/FerrLabs/FerrFlow/pull/716
|
|
8
|
+
---
|
|
9
|
+
|
|
10
|
+
Starting with v5.33, FerrFlow makes no network requests of its own beyond the git and forge operations you explicitly ask for. The anonymous-usage telemetry that previous versions sent on each command has been removed outright: not made opt-in, removed. There is nothing to disable and no data to think about.
|
|
11
|
+
|
|
12
|
+
There is a performance angle too, and it is not small. The old telemetry sent one event per bumped package and blocked the CLI's exit until every request completed. On a 50-package monorepo `check`, that was the difference between 1.5 seconds and 80 milliseconds. Most of what felt like "work" was the CLI waiting on its own telemetry. Removing it made the wait disappear for every command, on every repository.
|
|
13
|
+
|
|
14
|
+
Existing configurations need no changes: the `anonymousTelemetry` key (and its `telemetry` alias) remains accepted and simply does nothing, so no config warns or fails validation. The `FERRFLOW_TELEMETRY` and `DO_NOT_TRACK` environment variables still work on older versions: see the updated telemetry page for what ≤v5.32 sent and how to opt out there.
|
|
@@ -0,0 +1,20 @@
|
|
|
1
|
+
---
|
|
2
|
+
title: 'FerrFlow: Bitbucket support'
|
|
3
|
+
summary: FerrFlow now recognises Bitbucket Cloud repositories and handles their releases. No more scripting a hook to get automatic release tagging on Bitbucket.
|
|
4
|
+
date: 2026-07-18T13:00:00Z
|
|
5
|
+
product: ferrflow
|
|
6
|
+
type: new
|
|
7
|
+
prLink: https://github.com/FerrLabs/FerrFlow/pull/729
|
|
8
|
+
docsLink: https://ferrflow.com/docs/configuration/config-file
|
|
9
|
+
---
|
|
10
|
+
|
|
11
|
+
Bitbucket users used to fall through FerrFlow's forge detection and had to script release creation by hand. Now `bitbucket.org` remotes are detected automatically (or set `forge = "bitbucket"` explicitly), authenticated with `BITBUCKET_TOKEN`.
|
|
12
|
+
|
|
13
|
+
Bitbucket has no "release" object the way GitHub and GitLab do, so on Bitbucket a release **is** the annotated tag FerrFlow already creates and pushes: FerrFlow looks it up via the Bitbucket Cloud API and surfaces its URL in the release output. The changelog lives in your `CHANGELOG.md` and the tag message, as usual.
|
|
14
|
+
|
|
15
|
+
```toml
|
|
16
|
+
[workspace]
|
|
17
|
+
forge = "bitbucket" # or leave it "auto": bitbucket.org is detected
|
|
18
|
+
```
|
|
19
|
+
|
|
20
|
+
Pull-request release mode and Bitbucket Server / Data Center aren't supported yet. This first pass covers Bitbucket Cloud release creation, mirroring how Gitea/Forgejo landed.
|
|
@@ -0,0 +1,20 @@
|
|
|
1
|
+
---
|
|
2
|
+
title: 'FerrFlow: Robust BREAKING CHANGE detection'
|
|
3
|
+
summary: 'FerrFlow now recognises mixed-case, hyphenated, and lowercase `BREAKING CHANGE` footers, and a `!` typed inside the scope (`feat(api!):`), so a real breaking change no longer slips through and skips the major bump.'
|
|
4
|
+
date: 2026-07-18T11:00:00Z
|
|
5
|
+
product: ferrflow
|
|
6
|
+
type: fix
|
|
7
|
+
prLink: https://github.com/FerrLabs/FerrFlow/pull/727
|
|
8
|
+
docsLink: https://ferrflow.com/docs/reference/conventional-commits#accepted-footer-variants
|
|
9
|
+
---
|
|
10
|
+
|
|
11
|
+
A breaking change that FerrFlow doesn't recognise is quietly misclassified: it skips the major bump and ships a release that understates the change. Several real-world spellings of the `BREAKING CHANGE` marker used to fall through: now they don't.
|
|
12
|
+
|
|
13
|
+
Newly detected as breaking:
|
|
14
|
+
|
|
15
|
+
- **Case-insensitive footers**: `breaking-change:`, `breaking change:`, `Breaking Change:`, alongside the spec's `BREAKING CHANGE:` and `BREAKING-CHANGE:`.
|
|
16
|
+
- **`!` inside the scope**: `feat(api!):`, the common typo for `feat(api)!:`.
|
|
17
|
+
|
|
18
|
+
Detection stays strict where it matters, so a stray mention never triggers an accidental major bump: the footer still has to start a line and be followed by a colon **and a space**, the plural `BREAKING CHANGES:` and prose mentions are ignored, and a `!` that isn't right before the closing paren (`feat(a!b):`) is not a marker.
|
|
19
|
+
|
|
20
|
+
If your project used any of these variants, the next release will now correctly bump the major version. Run `ferrflow check` to preview.
|
|
@@ -0,0 +1,14 @@
|
|
|
1
|
+
---
|
|
2
|
+
title: 'FerrFlow: Faster repeat runs via commit-graph'
|
|
3
|
+
summary: 'On large repositories, FerrFlow now writes a git commit-graph on the first run so that later `check` and `release` walks are materially faster: a benefit that repeat users (pre-commit hooks, local dev, warm CI runners) get for free.'
|
|
4
|
+
date: 2026-07-18T12:00:00Z
|
|
5
|
+
product: ferrflow
|
|
6
|
+
type: perf
|
|
7
|
+
prLink: https://github.com/FerrLabs/FerrFlow/pull/728
|
|
8
|
+
---
|
|
9
|
+
|
|
10
|
+
FerrFlow's tag scans and commit walks already read a git commit-graph when one exists, but a fresh clone (every CI checkout) has a pack and no graph, so the speedup never kicked in where FerrFlow runs most.
|
|
11
|
+
|
|
12
|
+
Now, on a cold `check` (cache miss) or a real `release`, if the repository has no commit-graph and a history larger than ~1000 commits, FerrFlow writes one with `git commit-graph write --reachable`. On a 200-package, 10k-commit monorepo that trims the walk-heavy portion of a run by roughly 30% on every subsequent invocation.
|
|
13
|
+
|
|
14
|
+
It's transparent and best-effort: the write is skipped once a graph exists (so it's a one-time cost), skipped on small histories where it wouldn't pay off, skipped entirely on `--dry-run` so that stays read-only, and it never fails your command if git can't write the graph.
|
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
---
|
|
2
|
+
title: 'FerrFlow: ferrflow doctor'
|
|
3
|
+
summary: 'A new `ferrflow doctor` subcommand runs read-only diagnostics on your repo, config, and forge setup and prints a categorised report, so "is my setup sane?" has a first-class answer instead of grepping `--verbose` logs.'
|
|
4
|
+
date: 2026-07-18T09:00:00Z
|
|
5
|
+
product: ferrflow
|
|
6
|
+
type: new
|
|
7
|
+
prLink: https://github.com/FerrLabs/FerrFlow/pull/725
|
|
8
|
+
docsLink: https://ferrflow.com/docs/reference/cli#ferrflow-doctor
|
|
9
|
+
---
|
|
10
|
+
|
|
11
|
+
When a release behaved unexpectedly (a wrong bump, a tag that didn't move, no commits detected), the only recourse was `--verbose` and staring at logs. `ferrflow doctor` gives you a first-class health check instead.
|
|
12
|
+
|
|
13
|
+
```bash
|
|
14
|
+
ferrflow doctor # human report
|
|
15
|
+
ferrflow doctor --format json # machine-readable, stable for CI
|
|
16
|
+
ferrflow doctor --online # also check the GitHub API rate limit
|
|
17
|
+
```
|
|
18
|
+
|
|
19
|
+
It runs a series of read-only checks and groups them into five sections: **Repo** (git repository, commit history, clean working tree, remote, tags), **Config** (which config file wins, whether it parses, plus the full `ferrflow validate` suite), **Versioning** (strategy and each package's version), **Forge** (detected forge and whether an auth token is present), and **CI** (workflow files, and whether a workflow pins the FerrFlow action). Every check is green, a warning, or an error.
|
|
20
|
+
|
|
21
|
+
Run it on a fresh checkout and it explains exactly what's missing before your first release; run it on a misconfigured repo and it pinpoints the file or value at fault. The exit code is scriptable (`0` all green, `1` warnings, `2` errors), and `--format json` has a stable shape you can assert on in CI.
|
|
@@ -0,0 +1,19 @@
|
|
|
1
|
+
---
|
|
2
|
+
title: 'FerrFlow: ferrflow schema'
|
|
3
|
+
summary: 'A new `ferrflow schema` subcommand prints the config JSON schema that is now bundled into the binary, so editor tooling and pre-commit hooks can validate `.ferrflow.json` completely offline.'
|
|
4
|
+
date: 2026-07-18T10:00:00Z
|
|
5
|
+
product: ferrflow
|
|
6
|
+
type: new
|
|
7
|
+
prLink: https://github.com/FerrLabs/FerrFlow/pull/726
|
|
8
|
+
docsLink: https://ferrflow.com/docs/reference/cli#ferrflow-schema
|
|
9
|
+
---
|
|
10
|
+
|
|
11
|
+
The FerrFlow config schema has always been published at `ferrflow.com/schema/ferrflow.json` for editor autocompletion: great in VS Code or Zed, useless offline or in a pre-commit hook that can't reach the internet. `ferrflow schema` fixes that by shipping the schema inside the binary.
|
|
12
|
+
|
|
13
|
+
```bash
|
|
14
|
+
ferrflow schema # compact JSON to stdout
|
|
15
|
+
ferrflow schema --pretty # formatted
|
|
16
|
+
ferrflow schema --pretty --output ferrflow.schema.json
|
|
17
|
+
```
|
|
18
|
+
|
|
19
|
+
Write it to a file and point your editor at the local copy with `"$schema": "./ferrflow.schema.json"`, or generate it in CI to validate `.ferrflow.json` with no network call. The schema is embedded straight from the source of truth, so the bundled copy always matches the version you're running, and the command parses it before printing: a corrupt build artefact exits non-zero rather than emitting garbage.
|
|
@@ -0,0 +1,19 @@
|
|
|
1
|
+
---
|
|
2
|
+
title: 'FerrFlow: Auto-detect self-hosted forges'
|
|
3
|
+
summary: FerrFlow now recognises self-hosted GitLab, GitHub Enterprise, and Gitea/Forgejo instances automatically. No need to set `forge` by hand for a git host on your own domain.
|
|
4
|
+
date: 2026-07-18T14:00:00Z
|
|
5
|
+
product: ferrflow
|
|
6
|
+
type: new
|
|
7
|
+
prLink: https://github.com/FerrLabs/FerrFlow/pull/730
|
|
8
|
+
docsLink: https://ferrflow.com/docs/configuration/config-file
|
|
9
|
+
---
|
|
10
|
+
|
|
11
|
+
Until now, forge detection only knew the SaaS hostnames: a self-hosted GitLab or Gitea on `git.company.com` came back as "no forge", so you had to set `forge = "gitlab"` yourself to get automatic release creation.
|
|
12
|
+
|
|
13
|
+
Now, when FerrFlow doesn't recognise the remote's hostname, it probes the host's API over HTTPS to figure out what it is:
|
|
14
|
+
|
|
15
|
+
- a GitLab instance (self-hosted GitLab CE/EE),
|
|
16
|
+
- a GitHub Enterprise instance,
|
|
17
|
+
- or a Gitea / Forgejo instance.
|
|
18
|
+
|
|
19
|
+
The probe is unauthenticated, short (a ~2s timeout), best-effort, and cached, so a run checks a given host at most once, and a hostname FerrFlow already knows never touches the network. You only need to set `forge` explicitly now if your host isn't reachable over HTTPS or you'd rather skip the probe.
|
|
@@ -0,0 +1,32 @@
|
|
|
1
|
+
---
|
|
2
|
+
title: 'FerrFlow: Hooks see the whole release batch'
|
|
3
|
+
summary: 'Release hooks now receive `allPackages` (every package the run bumps, with its new version and bump type), so a monorepo hook can act on the batch, not just its own package.'
|
|
4
|
+
date: 2026-07-20T16:00:00Z
|
|
5
|
+
product: ferrflow
|
|
6
|
+
type: new
|
|
7
|
+
prLink: https://github.com/FerrLabs/FerrFlow/pull/741
|
|
8
|
+
docsLink: https://ferrflow.com/docs/configuration/config-file
|
|
9
|
+
---
|
|
10
|
+
|
|
11
|
+
A hook used to see only its own package. In a monorepo that made batch-aware automation awkward: a `postBump` on one package had no idea what else was being released alongside it.
|
|
12
|
+
|
|
13
|
+
Every hook now also gets `allPackages`: the full list of packages the run is bumping, each with its resolved new version and bump type. It's the same snapshot for every package's hook and for the batch-level `onSuccess` / `onError`, computed once after versions are settled, so even the first package's hook already sees the whole release.
|
|
14
|
+
|
|
15
|
+
Shell hooks read `FERRFLOW_ALL_PACKAGES_JSON`; JS/TS function hooks get `ctx.allPackages` as a real array:
|
|
16
|
+
|
|
17
|
+
```js
|
|
18
|
+
export default {
|
|
19
|
+
workspace: {
|
|
20
|
+
hooks: {
|
|
21
|
+
postBump(ctx) {
|
|
22
|
+
const summary = ctx.allPackages
|
|
23
|
+
.map((p) => `${p.name}@${p.version} (${p.bump})`)
|
|
24
|
+
.join(', ');
|
|
25
|
+
console.log(`Releasing: ${summary}`);
|
|
26
|
+
},
|
|
27
|
+
},
|
|
28
|
+
},
|
|
29
|
+
};
|
|
30
|
+
```
|
|
31
|
+
|
|
32
|
+
For a single-package repo it's just the one entry.
|
|
@@ -0,0 +1,35 @@
|
|
|
1
|
+
---
|
|
2
|
+
title: 'FerrFlow: Richer context for release hooks'
|
|
3
|
+
summary: Release hooks now receive the rendered changelog, the parsed commits, the list of bumped files, and whether the run is a monorepo or pre-release, both as `FERRFLOW_*` env vars and on the JS/TS `ctx` object.
|
|
4
|
+
date: 2026-07-20T12:00:00Z
|
|
5
|
+
product: ferrflow
|
|
6
|
+
type: new
|
|
7
|
+
prLink: https://github.com/FerrLabs/FerrFlow/pull/736
|
|
8
|
+
docsLink: https://ferrflow.com/docs/configuration/config-file
|
|
9
|
+
---
|
|
10
|
+
|
|
11
|
+
Hooks used to see only the basics: package name, old and new version, bump type, tag. That was enough to echo a message, but not enough to post a real release note or gate on what actually changed.
|
|
12
|
+
|
|
13
|
+
Every hook now gets the full picture. Shell hooks read new `FERRFLOW_*` environment variables; JS/TS function hooks get the same data as properties on the `ctx` object (both are built from one source, so they never drift):
|
|
14
|
+
|
|
15
|
+
- `changelog`: the rendered changelog section for this bump, in markdown.
|
|
16
|
+
- `commits`: the commits in the bump as structured objects (`hash`, `message`, `type`, `scope`, `breaking`), so you can branch on a breaking change instead of grepping a string.
|
|
17
|
+
- `bumpedFiles`: every file the release actually modified, with its format.
|
|
18
|
+
- `monorepo` and `isPrerelease`: flags to tell a workspace release apart from a single-package one, and a channel pre-release from a stable one.
|
|
19
|
+
|
|
20
|
+
`commits` and `bumpedFiles` arrive as real arrays in function hooks (`FERRFLOW_COMMITS_JSON` / `FERRFLOW_BUMPED_FILES_JSON` as JSON for shell hooks, ready to pipe through `jq`):
|
|
21
|
+
|
|
22
|
+
```js
|
|
23
|
+
export default {
|
|
24
|
+
workspace: {
|
|
25
|
+
hooks: {
|
|
26
|
+
postBump(ctx) {
|
|
27
|
+
const breaking = ctx.commits.filter((c) => c.breaking);
|
|
28
|
+
if (breaking.length) notify(`${breaking.length} breaking change(s) in ${ctx.newVersion}`);
|
|
29
|
+
},
|
|
30
|
+
},
|
|
31
|
+
},
|
|
32
|
+
};
|
|
33
|
+
```
|
|
34
|
+
|
|
35
|
+
The enrichment reaches every hook point: pre/post bump, commit, tag, publish, release, plus `onSuccess` / `onError`.
|
|
@@ -0,0 +1,20 @@
|
|
|
1
|
+
---
|
|
2
|
+
title: 'FerrFlow: Compare two versions with `diff`'
|
|
3
|
+
summary: 'A new `ferrflow diff v1.4.0..v1.6.0` command shows exactly what went into a version range: the commits and their bumps, the breaking changes, the files touched, and the changelog FerrFlow would generate for the range.'
|
|
4
|
+
date: 2026-07-21T15:00:00Z
|
|
5
|
+
product: ferrflow
|
|
6
|
+
type: new
|
|
7
|
+
prLink: https://github.com/FerrLabs/FerrFlow/pull/751
|
|
8
|
+
docsLink: https://ferrflow.com/docs/reference/cli
|
|
9
|
+
---
|
|
10
|
+
|
|
11
|
+
Sometimes you want to look at a release after the fact: what actually shipped between two versions, why the bump landed where it did, or you need release notes for a range you never tagged notes for. `ferrflow diff` answers that.
|
|
12
|
+
|
|
13
|
+
```bash
|
|
14
|
+
ferrflow diff v1.4.0..v1.6.0 # single-package repo
|
|
15
|
+
ferrflow diff api v1.4.0..v1.6.0 # monorepo: name the package
|
|
16
|
+
```
|
|
17
|
+
|
|
18
|
+
It prints the range's commits each tagged with its own bump (`major` / `minor` / `patch` / `none`), highlights the breaking changes, summarises the files changed, and renders the changelog section for the range using your changelog config. Add `--json` for a structured object you can pipe into anything.
|
|
19
|
+
|
|
20
|
+
Each side of the range is a version or tag: `v1.4.0` resolves to the tag directly in a single-package repo, or to the package's tag (`api@v1.4.0`) in a monorepo.
|