Support Rails 7.1

[cprodhomme]

• Version: 1.2.2

Since the 13 october, Rails release the version 7.1.0.beta1.

I thinks the official release of Rails 7.1 will be soon with amazing features ! Could you support this version ?

i saw some works on this PR : https://github.com/lynndylanhurley/devise_token_auth/pull/1606

Thanks ! 🙏

[scott-knight]

Would be nice to have an ETA on this.

[BenMukebo]

We're still waiting for the update cause currently I can't use devise_token_auth in th lastest vesion of ruby on rails (7.1.1)

[dhaigh]

sooner the better, 7.1.0 has been out since October 5 🙏

[smenor]

just a 「 me too 」

[up_the_irons]

I also want to use devise-token-auth but my new app is Rails 7.1.1 😭

[up_the_irons]

I found this fork: https://github.com/single-stop-tony/devise_token_auth

It makes a slight change to a part of the serialization and updated the gem spec to allow installation with Rails 7.1. No idea if it actually works now, or is a work in progress, but I'm going to give it a try.

[rohanmendon]

same here, want to use it on rails 7.1.2

[tbsvttr]

Same problem here.

[lsfernandes92]

I had the same error here and it seems that this stack overflow answer addressed my question regarding this issue

[orehmane]

That's a fine workaround, but it would nice to have a more proper version in rubygems.

[angusm73]

Adding the gem from github instead of rubygems does indeed work!

gem "devise_token_auth", ">= 1.2.0", git: "https://github.com/lynndylanhurley/devise_token_auth"

[karamat]

Facing this error

Your bundle is locked to devise_token_auth (1.2.2) from https://github.com/lynndylanhurley/devise_token_auth (at master@6b0659f), but that version can no longer be found in that source. That means the
author of devise_token_auth (1.2.2) has removed it. You'll need to update your bundle to a version other than devise_token_auth (1.2.2) that hasn't been removed in order to install.

Gemfile

gem 'devise_token_auth', '>= 1.2.2', git: "https://github.com/lynndylanhurley/devise_token_auth"

Environment

Rails 7.1.2 Ruby 3.3.0

[scott-knight]

What's the hold up here? I can't get graphql_devise upgraded without this update.

[groue]

Hello. I'm also waiting for Rails 7.1 for deferred foreign keys support.

[hatsu38]

@MaicolBen Thank you for your continuous maintenance. I really appreciate the convenience it provides!

I believe this ISSUE will be resolved once the version containing this PR #1606 is released. Is there anything missing for the release? If so, I am willing to help. Many people are looking forward to the release! Please make it happen!

[arp]

Same here. There are a few fixes that are already in master, so I had to port them manually in our app. Is there anything I could help with to release the new gem version?

[smenor]

Just adding a 「 me-too 」

On 27 Jan 2024, at 18:29, Artur Pyrogovskyi @.***> wrote:

Same here. There are a few fixes that are already in master, so I had to port them manually in our app. Is there anything I could help with to release the new gem version?

— Reply to this email directly, view it on GitHub https://github.com/lynndylanhurley/devise_token_auth/issues/1608#issuecomment-1913401004, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAPS37RKWEUE55DZCWADB7TYQWSV7AVCNFSM6AAAAAA4YICEOWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJTGQYDCMBQGQ. You are receiving this because you commented.

[StalemateInc]

Joining the flock of requesters - a stable version of Rails 7.1 was published four months ago and for some people explicit requirement of rails < 7.1 is a roadblock for upgrading. Can we at least extract the fixes for Rails 7.1 and have a patch level release?

[ManCodeB]

+1 from me to support Rails 7.1 🙂

This gem blocks me from upgrading - thank you in advance!

[saurabhbhatia]

+1 would really appreciate any movement on this

[ghost]

Joining the waiting crew, with a side of anxiety. 🫤😬

[jpayne]

I would greatly appreciate an update as well, so that Rails 7.1 upgrades can be completed.

[kenoga]

👍🏼

[VSidhArt]

Bump version, please We're all waiting for this update. It's blocked our rails upgrade.

[scott-knight]

I finally gave up waiting and created a fork. I'm not sure what the holdup is, but anyone is welcome to use the fork until they do their release.

[mgmodell]

It's been 5 months since any commits on this project and this blocker issue is open for about 6 months now. At what point does this get classified as abandoned? I, too, have been using my own fork, but a billion of those is not ideal. What do we do to reinvigorate this project?

[lynndylanhurley]

@mgmodell @scott-knight would either of you guys be interested in commit access to help push new releases?

[mgmodell]

@lynndylanhurley, I would be happy to support - as long as someone can be available to answer my questions as I work through it.

[mgmodell]

@lynndylanhurley, I'm hoping that we can move forward with this and I'll gladly take on the tasks, but the recent xz issue leaves me wanting oversight to make sure we can maintain the confidence of the community. Can we please move forward with this? Perhaps @scott-knight would like to share whatever load there might be? I've certainly got a lot to learn but there are clearly lots of people relying upon this software and I'll happily do my part (as my copious free time permits).

[scott-knight]

@mgmodell - I'm wondering if @lynndylanhurley as fallen off the earth. Seems unusual for something like this to go on as long as it has -- releases in the past have been consistent. Anyone know the status of @lynndylanhurley?