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.

Sign up for GitHub

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

Jump to bottom

keep track of crates that are whitelisted to be used even if yanked #6611

Merged
merged 9 commits into from
Feb 4, 2019
Merged

keep track of crates that are whitelisted to be used even if yanked #6611

merged 9 commits into from
Feb 4, 2019

Commits on Jan 29, 2019

  1. keep track of crates that are whitelisted to be used even if yanked

    @Eh2406
    Eh2406 committed Jan 29, 2019
    Configuration menu
    Copy the full SHA
    4400514 View commit details
    Browse the repository at this point in the history

  2. only whitelist packages we are keeping from the lockfile

    @Eh2406
    Eh2406 committed Jan 29, 2019
    Configuration menu
    Copy the full SHA
    4fb53e5 View commit details
    Browse the repository at this point in the history

  3. push the rest of the clones to the bottom

    @Eh2406
    Eh2406 committed Jan 29, 2019
    Configuration menu
    Copy the full SHA
    192073b View commit details
    Browse the repository at this point in the history

Commits on Jan 30, 2019

  1. [WIP] add tests why does this not pass!?

    @Eh2406
    Eh2406 committed Jan 30, 2019
    Configuration menu
    Copy the full SHA
    6953ef8 View commit details
    Browse the repository at this point in the history

  2. map_source for ReplacedSource

    @Eh2406
    Eh2406 committed Jan 30, 2019
    Configuration menu
    Copy the full SHA
    756f54c View commit details
    Browse the repository at this point in the history

Commits on Jan 31, 2019

  1. Revert "only whitelist packages we are keeping from the lockfile" 

    This reverts commit 4fb53e5
    @Eh2406
    Eh2406 committed Jan 31, 2019
    Configuration menu
    Copy the full SHA
    2f7eb42 View commit details
    Browse the repository at this point in the history

Commits on Feb 1, 2019

  1. Don't add the entire resolve to the yanked whitelist 

    If we're updating a crate then its previous version in the lock file is
no longer whitelisted. We may want to perhaps change this in the future!
    @alexcrichton
    alexcrichton committed Feb 1, 2019
    Configuration menu
    Copy the full SHA
    2bbce85 View commit details
    Browse the repository at this point in the history

  2. Fix a test assertion

    @alexcrichton
    alexcrichton committed Feb 1, 2019
    Configuration menu
    Copy the full SHA
    086a454 View commit details
    Browse the repository at this point in the history

Commits on Feb 3, 2019

  1. Update existing sources when whitelist modified 

    When sources already exist in a `PackageRegistry` and the whitelist is
updated in the package registry, be sure to update all the existing
sources to ensure that everyone gets the same view of the intended whitelist.
    @alexcrichton
    alexcrichton committed Feb 3, 2019
    Configuration menu
    Copy the full SHA
    4a2f810 View commit details
    Browse the repository at this point in the history