Redirect setup-rclone to AnchorFree pinned fork#8
Merged
Conversation
roman-kutashenko
approved these changes
Jul 1, 2026
ravi-bisht-pointwild
approved these changes
Jul 2, 2026
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.
Redirect
AnimMouse/setup-rcloneto our pinned forkWhat
Rewrites all uses of
AnimMouse/setup-rcloneto our forkAnchorFree/setup-rclone, pinned to a full-length commit SHA:Why
The upstream
AnimMouse/setup-rcloneis an action that references other actions internally (transitiveuses:). Those transitive references are not pinned to commit SHAs, and the upstream maintainer does not want to pinthem. That blocks us from enforcing full-length-SHA pinning across our actions, since the policy also applies to actions nested inside the composite actions we consume.
To resolve this, the fork
AnchorFree/setup-rclonewas created. The only difference in the fork is that its internal/transitive action references are pinned to commit SHAs. There are no behavioral changes — it does exactly what upstream does.Impact
setup-rclonereferences now resolve to an immutable commit SHA, end toend (including transitive actions), satisfying SHA-pinning.