Recent fake release (0.1.2 / 7.6) broke CI

[jdleonard]

I observed a CI script that includes the following:

composer global require consolidation/cgr
cgr pantheon-systems/terminus

yield:

Using version ^7.6 for pantheon-systems/terminus

and break.

Perhaps the script should have specified version constraints, but this fake release seems to be what triggered it. I suspect others may run into this.

[jdleonard]

cc release author @namespacebrian

[greg-1-anderson]

I deleted the tag for that release through the GitHub UI but have not tested to see if that was sufficient to correct the problem.

[namespacebrian]

I accidentally pushed a 7.6.5 to the main terminus repo on Friday. (I'd intended to push it to a separate development repo which was a second remote in my local clone.) I saw the mistake and deleted the tag from Github 5 minutes later, but that wasn't fast enough to prevent composer from picking it up as a new package.

Composer was briefly installing the package successfully on Friday before I deleted the tag. After that, attempts to install the 7.6 version via composer failed for a while until packagist.org removed the release. Local composer instances that still had the 7.6 version in their cache would still try to install it, however.

@jdleonard are you still experiencing the error?

(edit: The 0.1.2 tag was also accidentally pushed, but I missed deleting that one on Friday.)

[jdleonard]

I updated the repos I'm responsible for with a version constraint, which resolved the problem for me. I'm on my way out the door for some vacation so unfortunately I don't have time to debug further. Thanks for your follow-up!