Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Track which commands a registry supports in its config.json #4747

Closed
wants to merge 3 commits into from

Commits on Nov 18, 2017

  1. Registries list which commands they support

    The registry config.json contains an extra field, "commands",
    an object. The fields of this object each is a command, which
    records which versions (if any) of this command that registry
    supports. A complete registry, as of today, would have these
    commands:
    
    ```json
    {
        "login": ["v1"],
        "publish": ["v1"],
        "owner": ["v1"],
        "search": ["v1"],
        "yank": ["v1"]
    }
    ```
    Without Boats committed Nov 18, 2017
    Configuration menu
    Copy the full SHA
    ee37f6e View commit details
    Browse the repository at this point in the history

Commits on Nov 19, 2017

  1. Add a check in the login flow.

    Prior to this commit, the login flow for registries other than the
    default does not support the token pasting flow. Now, if the host
    flag is specified, or the registry claims to support the "v1" flow,
    we enter the token pasting flow.
    Without Boats committed Nov 19, 2017
    Configuration menu
    Copy the full SHA
    b1d5504 View commit details
    Browse the repository at this point in the history

Commits on Nov 26, 2017

  1. Fix search test.

    Without Boats committed Nov 26, 2017
    Configuration menu
    Copy the full SHA
    9b0dc6e View commit details
    Browse the repository at this point in the history