The saga of Drupal link-link

Are your builds failing because of this?

  - Installing drupal/link-link (dev-1.x 0058c8a)
    Cloning 0058c8ae3b6e61f41fd4f407b50c28a5e51688ef
    0058c8ae3b6e61f41fd4f407b50c28a5e51688ef is gone (history was rewritten?)

[RuntimeException]                                                                                                                             
  Failed to execute git checkout '0058c8ae3b6e61f41fd4f407b50c28a5e51688ef' -- && git reset --hard '0058c8ae3b6e61f41fd4f407b50c28a5e51688ef' -- 
  fatal: reference is not a tree: 0058c8ae3b6e61f41fd4f407b50c28a5e51688ef

You must have the Redirect module! Don't worry, you can keep your Redirect module. Applying the patch from Redirect module: Update composer.json and namespace module dependencies, or at least using a dev version, will be necessary for now, though.

We're using the latest dev.

Run composer update, and the so-called "drupal/link-link" gets... moved? (See ridiculous diff below, if you are so inclined.)

What looks more promising is the one place that was requiring drupal/link-link, the Redirect module, is no longer requiring it. Why is it still in our composer.lock file then? Oh well, let's try composer update again:

vagrant@mass:/vagrant$ composer update
Gathering patches for root package.
Loading composer repositories with package information
Updating dependencies (including require-dev)
Deleting web/modules/contrib/link-link - deleted
Package codegyre/robo is abandoned, you should avoid using it. Use consolidation/robo instead.
Writing lock file
Generating autoload files

Well, that did it. Again, you need the latest dev (pre-patch) for this double composer update to work. With the patch, just one composer update should do.

Of course, also make sure you're not directly requiring the doesn't-really-exist-for-Drupal-8 module with a line like "drupal/link-link": "@dev", in your composer.json.