kotovalexarian-likes-github/heartcombo--devise
1
0
Fork 0
mirror of https://github.com/heartcombo/devise.git synced 2022-11-09 12:18:31 -05:00
Code Releases Activity

Update CHANGELOG [ci skip]

Browse source
This commit is contained in:
Lucas Mazza 2014-10-03 14:20:31 -03:00
parent 8e5c098e3a
commit 9b49e89ebd
1 changed files with 13 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
CHANGELOG.md
View file

@ -1,19 +1,29 @@
### Unreleased
* enhancements
* bugfixes
### 3.4.0
* enhancements
* Support added for Rails 4.2. Devise now depends on the `responders` gem due
the extraction of the `respond_with` API from Rails. (by @lucasmazza)
* The Simple Form templates follow the same change from 3.3.0 by using `Log in` and adding
a hint about the minimum password length when `validatable` is enabled (by @aried3r)
a hint about the minimum password length when `validatable` is enabled. (by @aried3r)
* Remove reloading of routes when eager loading is enabled. This change was added during Rails 3 and it doesn't seem to be relevant to currently supported Rails versions (by @fgro)
* Controller generator added as `devise:controllers SCOPE`. You can use the `-c` flag
to pick which controllers (`unlocks`, `confirmations`, etc) you want to generate. (by @Chun-Yang)
* Removed the hardcoded references for "email" in the flash messages. If you are using
different attributes as the `authentication_keys` they will be interpolated in the
messages instead. (by @timoschilling)
* bug fix
* Fixed a regression where the devise generator would fail with a `ConnectionNotEstablished`
exception when executed inside a mountable engine
exception when executed inside a mountable engine. (by @lucasmazza)
* Ensure to return symbols in find_scope! fixing a previous regression from 3.3.0 (by @micat)
* Ensure all causes of failed login have the same error message (by @pjungwir)
* The `last_attempt_warning` now takes effect when generating the unauthenticated
message for your users. To keep the current behavior, this flag is now `true`
by default. (by @lucasmazza)
by default. (by @lucasmazza)
### 3.3.0