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

[BackPort] Conservative updates #6655

Merged
merged 10 commits into from
Feb 12, 2019
Merged

[BackPort] Conservative updates #6655

merged 10 commits into from
Feb 12, 2019

Commits on Feb 12, 2019

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

    @Eh2406
    Eh2406 committed Feb 12, 2019
    Configuration menu
    Copy the full SHA
    ab3d218 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 Feb 12, 2019
    Configuration menu
    Copy the full SHA
    4481276 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 Feb 12, 2019
    Configuration menu
    Copy the full SHA
    865a847 View commit details
    Browse the repository at this point in the history

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

    @Eh2406
    Eh2406 committed Feb 12, 2019
    Configuration menu
    Copy the full SHA
    6fa6602 View commit details
    Browse the repository at this point in the history

  5. map_source for ReplacedSource

    @Eh2406
    Eh2406 committed Feb 12, 2019
    Configuration menu
    Copy the full SHA
    d611ba1 View commit details
    Browse the repository at this point in the history

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

    This reverts commit 4fb53e5
    @Eh2406
    Eh2406 committed Feb 12, 2019
    Configuration menu
    Copy the full SHA
    a539ea3 View commit details
    Browse the repository at this point in the history

  7. 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 @Eh2406
    alexcrichton authored and Eh2406 committed Feb 12, 2019
    Configuration menu
    Copy the full SHA
    3b45cf7 View commit details
    Browse the repository at this point in the history

  8. Fix a test assertion

    @alexcrichton @Eh2406
    alexcrichton authored and Eh2406 committed Feb 12, 2019
    Configuration menu
    Copy the full SHA
    da3028b View commit details
    Browse the repository at this point in the history

  9. 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 @Eh2406
    alexcrichton authored and Eh2406 committed Feb 12, 2019
    Configuration menu
    Copy the full SHA
    18f7f17 View commit details
    Browse the repository at this point in the history

  10. switch from unused_imports to deprecated to test unfixable warnings 

    The unused_imports warning is going to emit fixable suggestions in the
near future, but that means parts of the cargo's test suite will break.
This commit switches the tests to use the deprecated warning, which
*shouldn't* be fixable at all.
    @pietroalbini @ehuss
    pietroalbini authored and ehuss committed Feb 12, 2019
    Configuration menu
    Copy the full SHA
    63412be View commit details
    Browse the repository at this point in the history