Beta pushed to master

[bmulholland]

There's no published version of this gem. #31

We're using the master branch, following this comment: #37 (comment)

I'll note this says "this is something we will investigate why it wasn't published publicly." But that never happened.

However, f2db33d is pushing pretty significant changes.

So: what's the correct way for us to use the latest, stable version of this? Because the current state of things, leaving release status in purgatory, is unstable and creating needless risk for us.

[bmulholland]

Oh, it looks like 2.2 WAS pushed, but without an update to the issue...

Does that mean #31 should be closed?

[sherwinski]

Hey @bmulholland and thanks for reaching out. You're right that #31 should be closed; it looks like I forgot to update the issue after publishing the v2 gem. I'll also add that users should pin their gem version to 2.2.0 (as opposed to the default branch) while we work on the next major release.

what's the correct way for us to use the latest, stable version of this? Because the current state of things, leaving release status in purgatory, is unstable and creating needless risk for us.

I hear your concerns here. To give you some context, we are playing catch up in this library (and others) to get everything lined up with the OneSignal API while also patching in some long-needed fixes. To that end, we are introducing some significant changes (as you mentioned) and prepping v5 of this gem for an initial beta release. After a requisite period of testing/addressing user feedback, we will release the gem for general use in a more stable channel.

Hopefully that addresses your concerns. Please let me know if you have any other questions I can help answer.

[bmulholland]

Yeah, I think having a stable version released works well. Thank you! Closing :)

[bmulholland]

(And good luck with the updates!)