ci: bump FerrFlow action pin to v5.7.0#110
Merged
Merged
Conversation
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
1 participant
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.
@
What
Bumps the FerrFlow action pin in the reusable release workflow from
604314b # v5to the v5.7.0 release commitf6b2a3c # v5.7.0.Why
The action installs the
latestFerrFlow binary at runtime, so behaviour already tracks the newest release — but the pinned wrapper SHA and its# v5comment were stale (predating the publishers feature) and misleading. This realigns the wrapper with the binary it installs. Relevant now that Kit publishes to Kellnr through FerrFlow declarative publishers (FerrLabs/Kit#120).The
v5floating tag in FerrLabs/FerrFlow is stuck at v5.2.3 and does not track newer v5.x releases (tracked separately), so this uses the explicit v5.7.0 release commit rather than the floating tag.Closes #109
@