chore(deps): update ferrlabs/ferrflow action to v7 - #240
Open
ferrlabs-renovate[bot] wants to merge 1 commit into
Open
ferrlabs-renovate[bot] wants to merge 1 commit into
ferrlabs-renovate[bot] wants to merge 1 commit into
Conversation
![ferrfleet[bot]](https://avatars.githubusercontent.com/in/4354888?s=60&v=4){kind=small}
There was a problem hiding this comment.
Bump FerrLabs/FerrFlow v5 → v7, pinned by SHA (8825c0a... → 7a34f3e...).
What changed (v6, v7 release notes):
- v6.0.0: relicense MPL-2.0 → MIT (no code impact), plus a fix that verifies the downloaded release archive against SHA256SUMS before extracting.
- v7.0.0:
feat(commits)!: configurable commit formats via workspace.commitFormats— the only breaking change in the range.
What breaks here: nothing. .github/workflows/ci.yml invokes the action with only bot: true and dry_run: ${{ inputs.dry_run }} — no workspace.commitFormats or other commit-format config is used anywhere in the repo (checked, no .ferrflow.* config file exists). The v7 breaking change doesn't touch this usage.
CI: all checks green (Lint, Test, security scans, PR title check).
Uneventful major bump — safe to merge.
ferrlabs-renovate
Bot
force-pushed
the
renovate/major-ferrlabs-actions-(weekly)
branch
23 times, most recently
from
September 7, 2026 12:15
dbf62f7 to
ebd174e
Compare
ferrlabs-renovate
Bot
force-pushed
the
renovate/major-ferrlabs-actions-(weekly)
branch
2 times, most recently
from
September 14, 2026 12:31
f1fdfc1 to
605c97e
Compare
ferrlabs-renovate
Bot
force-pushed
the
renovate/major-ferrlabs-actions-(weekly)
branch
3 times, most recently
from
September 16, 2026 16:42
a52d944 to
358956e
Compare
ferrlabs-renovate
Bot
force-pushed
the
renovate/major-ferrlabs-actions-(weekly)
branch
from
September 17, 2026 04:33
358956e to
6ac5790
Compare
ferrlabs-renovate
Bot
force-pushed
the
renovate/major-ferrlabs-actions-(weekly)
branch
from
September 17, 2026 11:30
6ac5790 to
d759f41
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v5→v7Release Notes
FerrLabs/FerrFlow (FerrLabs/FerrFlow)
v7.21.3Compare Source
[7.21.3] - 2026-09-16
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.21.2Compare Source
[7.21.2] - 2026-09-16
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.21.1Compare Source
[7.21.1] - 2026-09-07
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.21.0Compare Source
[7.21.0] - 2026-09-07
Features
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.2Compare Source
[7.20.2] - 2026-09-07
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.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
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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.