chore(deps): update ferrlabs/ferrflow action to v7.20.1 - #256
Conversation
![ferrfleet[bot]](https://avatars.githubusercontent.com/in/4354888?s=60&v=4){kind=small}
There was a problem hiding this comment.
Uneventful bump, no breaking change touching this repo, CI green.
Checked the 9 releases between v7.11.1 and v7.20.1: all bug fixes and additive features (PyPI trusted publishing, buildMetadata config, doctor/rollback commands, etc). The one change with removal semantics, fix(config): drop the dead anonymousTelemetry field (v7.13.6), doesn't apply here — .ferrflow at the repo root has no anonymousTelemetry key. The workspace/publisher config used by this repo (latestTag, releaseCommitBody, recoverMissedReleases, skipCi, deferPublish, docker/helm publishers) is untouched by any changelog entry in range.
publish.yml only invokes the action with mode: publish, no other inputs, so nothing in the new config surface (buildMetadata override, calver-short-seq, galaxyyml format) is exercised.
CI is green (Build, Test, Lint, Security, kind smoke test). Note the publish job itself only runs on tag push or workflow_dispatch, so this PR's checks don't actually execute the bumped action — that's a pre-existing gap in this workflow's coverage, not something introduced here. SonarQube shows "cancelled" rather than pass/fail, unrelated to the version bump.
SonarQube — aucune nouvelle issueComparaison entre le projet bac à sable de cette PR et la branche par défaut : SonarQube Community n'analyse pas les PR, ce delta est calculé côté CI. Détail |
This PR contains the following updates:
v7.11.1→v7.20.1Release Notes
FerrLabs/FerrFlow (FerrLabs/FerrFlow)
v7.20.1Compare Source
[7.20.1] - 2026-09-06
Bug Fixes
Performance
Binary
Note: every competitor is a Node.js package — none ship a native binary, so this section can only show
ferrflow. Cross-tool comparisons live in the Npm section.Docker
Note: no competitor publishes a first-party Docker image that is comparable to
ghcr.io/ferrlabs/ferrflow(a single static binary). Wrapping the Node tools innode:ltswould only re-timenode startup + npm + the toolalready measured in the Npm section, so this section is intentionally limited toferrflow.Npm
Install footprint
v7.20.0Compare Source
[7.20.0] - 2026-09-05
Features
Performance
Binary
Note: every competitor is a Node.js package — none ship a native binary, so this section can only show
ferrflow. Cross-tool comparisons live in the Npm section.Docker
Note: no competitor publishes a first-party Docker image that is comparable to
ghcr.io/ferrlabs/ferrflow(a single static binary). Wrapping the Node tools innode:ltswould only re-timenode startup + npm + the toolalready measured in the Npm section, so this section is intentionally limited toferrflow.Npm
Install footprint
v7.19.2Compare Source
[7.19.2] - 2026-09-05
Bug Fixes
Performance
Binary
Note: every competitor is a Node.js package — none ship a native binary, so this section can only show
ferrflow. Cross-tool comparisons live in the Npm section.Docker
Note: no competitor publishes a first-party Docker image that is comparable to
ghcr.io/ferrlabs/ferrflow(a single static binary). Wrapping the Node tools innode:ltswould only re-timenode startup + npm + the toolalready measured in the Npm section, so this section is intentionally limited toferrflow.Npm
Install footprint
v7.19.1Compare Source
[7.19.1] - 2026-09-05
Bug Fixes
Performance
Binary
Note: every competitor is a Node.js package — none ship a native binary, so this section can only show
ferrflow. Cross-tool comparisons live in the Npm section.Docker
Note: no competitor publishes a first-party Docker image that is comparable to
ghcr.io/ferrlabs/ferrflow(a single static binary). Wrapping the Node tools innode:ltswould only re-timenode startup + npm + the toolalready measured in the Npm section, so this section is intentionally limited toferrflow.Npm
Install footprint
v7.19.0Compare Source
[7.19.0] - 2026-09-04
Features
Performance
Binary
Note: every competitor is a Node.js package — none ship a native binary, so this section can only show
ferrflow. Cross-tool comparisons live in the Npm section.Docker
Note: no competitor publishes a first-party Docker image that is comparable to
ghcr.io/ferrlabs/ferrflow(a single static binary). Wrapping the Node tools innode:ltswould only re-timenode startup + npm + the toolalready measured in the Npm section, so this section is intentionally limited toferrflow.Npm
Install footprint
v7.18.0Compare Source
[7.18.0] - 2026-09-04
Features
Performance
Binary
Note: every competitor is a Node.js package — none ship a native binary, so this section can only show
ferrflow. Cross-tool comparisons live in the Npm section.Docker
Note: no competitor publishes a first-party Docker image that is comparable to
ghcr.io/ferrlabs/ferrflow(a single static binary). Wrapping the Node tools innode:ltswould only re-timenode startup + npm + the toolalready measured in the Npm section, so this section is intentionally limited toferrflow.Npm
Install footprint
v7.17.1Compare Source
[7.17.1] - 2026-09-04
Bug Fixes
Performance
Binary
Note: every competitor is a Node.js package — none ship a native binary, so this section can only show
ferrflow. Cross-tool comparisons live in the Npm section.Docker
Note: no competitor publishes a first-party Docker image that is comparable to
ghcr.io/ferrlabs/ferrflow(a single static binary). Wrapping the Node tools innode:ltswould only re-timenode startup + npm + the toolalready measured in the Npm section, so this section is intentionally limited toferrflow.Npm
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate CLI.