Widen que version requirement to allow v1.0.0.beta5

[ajoneil]

No description provided.

[hlascelles]

Thanks for this! Will cut a gem after work today.

[paduszynski]

Thanks for it :)

[hlascelles]

Hmm... I have built a new version, but no matter what I do, rubygems prevents me from publishing it.

You have enabled multi-factor authentication. Please enter OTP code.
Code:   111111
Your OTP code is incorrect. Please check it and retry.

The codes are right, I can log into the UI with the same code at the same time. I have tried 6 times over several minutes. I am at a loss... I will keep trying.

[hlascelles]

Aha, it was my API key (which has now been renamed legacy-api-key by rubygems?). It looks like, for whatever reason, legacy keys don't support OTP.

[hlascelles]

Gem 4.2.0 published! https://rubygems.org/gems/que-scheduler/versions/4.2.0

[ajoneil]

Great, thank you for the quick turnaround :)

…

On Fri, 7 Jan 2022, 6:56 am Harry Lascelles, ***@***.***> wrote: Gem 4.2.0 published! https://rubygems.org/gems/que-scheduler/versions/4.2.0 — Reply to this email directly, view it on GitHub <#303 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADQMNWK7U4PRV5AS6MKHDLUUXXYHANCNFSM5LLLYQBQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.***>