-
Notifications
You must be signed in to change notification settings - Fork 190
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.
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
Recent fake release (0.1.2 / 7.6) broke CI #2202
Comments
cc release author @namespacebrian |
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. |
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.) |
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! |
I observed a CI script that includes the following:
yield:
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.
The text was updated successfully, but these errors were encountered: