prepping for 0.4.0 release

Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    sentient_user (0.3.3)
+    sentient_user (0.4.0)
       railties (>= 3.1)
 
 GEM
@@ -27,7 +27,7 @@ GEM
     json (1.8.3)
     minitest (4.7.5)
     minitest_should (0.3.1)
-    multi_json (1.11.2)
+    multi_json (1.12.1)
     rack (1.5.5)
     rack-test (0.6.3)
       rack (>= 1.0)
@@ -64,4 +64,4 @@ DEPENDENCIES
   turn
 
 BUNDLED WITH
-   1.11.2
+   1.13.1

README.rdoc

@@ -17,11 +17,18 @@ How often have you needed to access the current user in your models?  This happe
 == Assumptions and limitations
 * Your user model is called 'User'.
 * You have a current_user method available to your controllers
-* You will write your own tests to cover this code.
+* You will write your own tests to cover this code. The gem has tests, but its up to you to make sure you use this ability wisely.
 
 If those assumptions don't work for you, feel free to unpack and hack.  It's simple enough code to change.  I purposefully didn't want to complicate it with an initializer, several config options, etc. as all that would blur this delightfully simple piece of code.
 
 
+== Recent Changes
+This gem has been remarkably stable for many years and many iterations of rails.  The recent deprecation of before_filter in favor of before_action is making me update it.
+
+* 0.4.0 - for use on Rails 5 and beyond.
+* 0.3.3 - for versions prior to rails 5.
+
+
 == Note on Patches/Pull Requests
 
 * Fork the project.

lib/sentient_user/version.rb

@@ -1,3 +1,3 @@
 module SentientUser
-  VERSION = "0.3.3"
+  VERSION = "0.4.0"
 end