You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+27Lines changed: 27 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,6 +8,33 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
8
8
9
9
## [Unreleased]
10
10
11
+
## [3.0.7] - 2021-03-23
12
+
13
+
### Fixed
14
+
15
+
-\[ActiveRecord\] Fixed [#110](https://github.com/omniauth/omniauth-identity/issues/110) which prevented `OmniAuth::Identity::Models::ActiveRecord`-based records from saving.
-\[Model\] Only define `::create`, `#save`, and `#persisted?` when not already defined.
19
+
-\[Model\] Restore original `info` functionality which set `name` based on `first_name`, `last_name`, or `nickname`
20
+
21
+
### Changed
22
+
23
+
- Upgraded to a newer `OmniAuth::Identity::SecurePassword` ripped from [Rails 6-1-stable](https://github.com/rails/rails/blob/6-1-stable/activemodel/lib/active_model/secure_password.rb)
24
+
- Aeons ago the original was ripped from Rails 3.1, and frozen in time.
25
+
While writing specs, it was discovered to be incompatible with this gem's Sequel adapter.
26
+
- Specs validate that the new version does work.
27
+
In any case, the ripped version is only used when the `has_secure_password` macro is not yet defined in the class.
28
+
29
+
### Added
30
+
31
+
- New specs to cover real use cases and implementations of each ORM model adapter that ships with the gem:
32
+
- ActiveRecord (Polyglot - Many Relational Databases)
Please contribute some documentation if you have the gumption! The maintainer's time is limited, and sometimes the authors of PRs with new options don't update the _this_ readme. 😭
267
268
269
+
## Contributing
270
+
271
+
1. Fork it
272
+
2. Create your feature branch (`git checkout -b my-new-feature`)
273
+
3. Commit your changes (`git commit -am ‘Added some feature’`)
274
+
4. Push to the branch (`git push origin my-new-feature`)
275
+
5. Make sure to add tests for it. This is important so I don’t break it in a future version unintentionally.
276
+
- NOTE: In order to run *all* the tests you will need to have the following databases installed, configured, and running.
277
+
1.[RethinkDB](https://rethinkdb.com), an open source, real-time, web database, [installed](https://rethinkdb.com/docs/install/) and [running](https://rethinkdb.com/docs/start-a-server/), e.g.
0 commit comments