Always a fun one when things that were working just fine suddenly break.
In my case, the thing that broke was the composer update command after upgrading my GitLab server to version 11.
And the way in which the problem manifest was as follows:
$ composer update
Loading composer repositories with package information
[Composer\Downloader\TransportException]
The "https://gitlab.server/api/v3/projects/my/bundle" file could not be downloaded (HTTP/1.1 410 Gone)
For clarity, this is a personal / internal bundle that I made and share between a bunch of projects. This bundle lives on my internal GitLab server, and as such, requires a little extra config to work properly.
The solution to this problem, in my case, was to update composer.
Yes, shamefully I was 3 minor versions out of date:
$ composer -v
______
/ ____/___ ____ ___ ____ ____ ________ _____
/ / / __ \/ __ `__ \/ __ \/ __ \/ ___/ _ \/ ___/
/ /___/ /_/ / / / / / / /_/ / /_/ (__ ) __/ /
\____/\____/_/ /_/ /_/ .___/\____/____/\___/_/
/_/
Composer version 1.3.2 2017-01-27 18:23:41
After updating composer:
$ composer self-update Updating to version 1.6.5 (stable channel).
Everything began to work as expected.
I do love an easy fix. Thanks to all at the composer team, I do still remember life without this tool. And it wasn’t fun.
