Latest gem breaks production due to a listen gem requirement

[jhubert]

@jkodumal I don't have a lot of details on this. I'm on the road and my team just let me know they had to roll this back. Wanted to let you know asap. I'll share more details when I get them.

[eli-darkly]

Hi. By "latest gem" do you mean v5.4.0 or v5.4.1? There's a known problem in 5.4.0 involving that gem requirement, but it was thought to be fixed in 5.4.1.

[jhubert]

Sorry, 5.4.0 We’ll check out 5.4.1 Any issue or info on the problem in 5.4.0? I didn’t see anything reported.

…

On Thu, Nov 8, 2018 at 3:10 PM Eli Bishop ***@***.***> wrote: Hi. By "latest gem" do you mean v5.4.0 or v5.4.1? There's a known problem in 5.4.0 involving that gem requirement, but it was thought to be fixed in 5.4.1. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#112 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAANOIbTIreO_1PW7kGe6m1DzvL177d0ks5utI-vgaJpZM4YVX-n> .

[eli-darkly]

It's mentioned in the release notes and changelog for 5.4.1, but we should have unpublished the 5.4.0 release to be on the safe side (although you might have already acquired it before we found the problem). I'll do that now. Sorry about the trouble.

[jhubert]

No worries. Thankfully it broke in the deploy so the issue never hit customers. We use a service that creates pull-requests for new gem versions once a week, so we often don’t see new version updates until the end of a week. Unpublishing the gem would have caught it because the tests would have failed.

…

On Thu, Nov 8, 2018 at 3:17 PM Eli Bishop ***@***.***> wrote: It's mentioned in the release notes and changelog for 5.4.1, but we should have unpublished the 5.4.0 release to be on the safe side (although you might have already acquired it before we found the problem). I'll do that now. Sorry about the trouble. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#112 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAANOKDjMvkjxP0_MkEVlrNSAt0GoAX-ks5utJF1gaJpZM4YVX-n> .

[eli-darkly]

It's been pulled now and I've also deleted the release from Github. Sorry again.