fix(cg-actions): resolve mirrors via org index (fewer false "no equivalent") - #6
Closed
tylerpaxton wants to merge 1 commit into
Closed
fix(cg-actions): resolve mirrors via org index (fewer false "no equivalent")#6tylerpaxton wants to merge 1 commit into
tylerpaxton wants to merge 1 commit into
Conversation
…alent")
Mirror lookup previously guessed two exact names (chainguard-actions/{owner}-{repo},
{repo}) and did a direct repo check. That produced false "no equivalent" results
when a PUBLIC mirror existed under a name the guess didn't match exactly — most
notably subpath actions (actions/cache/restore) and case differences (azure/cli
-> Azure-cli).
Now build a one-time index of all public, non-archived chainguard-actions repos
and resolve candidates against it case-insensitively, dropping any subpath. Private
/ in-development repos are never in the index, so they're still never recommended.
Falls back to the old per-candidate check if the org listing can't be fetched.
Verified: actions/cache/restore and azure/cli now resolve (previously ❌);
docker/build-push-action (private) and renovatebot/github-action (absent) still ❌.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Contributor
Author
|
Superseded by #9, which consolidates this into a single reviewable PR (one commit per change, single VERSION bump). |
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.
Problem
Mirror lookup guessed two exact repo names (
chainguard-actions/{owner}-{repo}, then{repo}) and checked each directly. When a public mirror existed under a name the guess didn't match exactly, the action was wrongly reported ❌ no equivalent. Concretely:actions/cache/restoresplit toactions/cache/restore, producing an invalid guess → ❌, even thoughchainguard-actions/actions-cacheexists.azure/clivs the mirrorAzure-cli.Fix
Build a one-time index of all public, non-archived
chainguard-actionsrepos and resolve the candidate names against it case-insensitively, dropping any subpath. Because the index only contains public repos, private/in-development mirrors (e.g.docker/build-push-action) are still never recommended. Falls back to the previous per-candidate check if the org listing can't be fetched.Verified (against real catalog)
actions/cache/restorechainguard-actions/actions-cache@v6.1.0azure/clichainguard-actions/Azure-cli@v2.2.0docker/build-push-action(private)renovatebot/github-action(absent)Note: this is the durable interim until equivalence is driven by
chainctl actions catalog.🤖 Generated with Claude Code