New release compatible with devise 4

[mrdomino]

0.10.0 requires devise < 4, so it's impossible to use both the latest devise and the latest devise_security_extension. It'd be great to have a release from current master, which doesn't seem to have this problem.

[borisrorsvort]

@manno any update on this one?

[manno]

I'm not using devise_security_extension myself and I don't have access to the rubygems account (#178).
However I do still have commit access, so I could merge a PR to make master work with modern Rails.

Long-term, someone with rubygems access needs to step up or the actual users will have to fork the project. It would really benefit from some active maintainers. That would be a good opportunity to split this into smaller gems, too.

[borisrorsvort]

@manno tried this one and it seems to work fine #195

[manno]

@borisrorsvort #195 is now merged

[mvz]

@manno what needs to happen for a new gem to be pushed to rubygems?

[khataev]

+1 for compability with devise 4.0

[ericenns]

Any update on this I need Devise 4.2 so I can deploy via sub path

[v3rron]

Same here, can't install this Gem due to dependency conflict with Devise 4.2.
Please push the update to RubyGems.

[Drenmi]

Phatworx website is no longer available, so is it safe to assume that no-one is maintaining this anymore?

[adamdullenty]

+1 on not being able to install this due to dependency conflict with Devise 4.2.

[natebird]

I'm not trying to fork or take over the project but if you'd like to use my repo I've updated it for Rails 5 / Devise 4 compatibility.

https://github.com/natebird/devise_security_extension

I also changed the gem tag to 0.10.1 just so I could differentiate versions in my software.

[dillonwelch]

@natebird FYI I have #216 up if you need Ruby 2.4 support, I can make a PR on your fork too.

[natebird]

That would be nice. Thanks! Nate

…

On Apr 5, 2017, at 1:28 PM, Dillon Welch ***@***.***> wrote: @natebird <https://github.com/natebird> FYI I have #216 <#216> up if you need Ruby 2.4 support, I can make a PR on your fork too. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#192 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAR0HgeDwBEn0KTBjduJchssaZgna6Vks5rs886gaJpZM4JRRYG>.

[toobulkeh]

@natebird would you be willing to fork this into a different Gem? even just differently named so we can use rubygems over some kind of git reference would definitely help

[dillonwelch]

The approach I'd like to see is getting these into the main devise gem

[vinagrito]

@traxanos

[natebird]

@toobulkeh, @oniofchaos -
I would like to investigate the following solutions:

• See if @traxanos and other owners are still interested in maintaining this gem. If not then see if we can't get some fresh blood to cleanup and maintain it.
• It would also be good to investigate the possibility of merging this into the devise gem. I'm not sure the history but I think this gem has many features that can be used by nearly all devise users.
• If all of this fails then we should just fork this into a new gem so this code can be maintained more regularly. There seems to be at least some interest in keeping this extension going.

[mvz]

There's a forked gem devise-security: https://github.com/devise-security/devise-security