CHANGELOG.md in raygun4ruby-1.2.1 vs CHANGELOG.md in raygun4ruby-1.3.0

@@ -1,4 +1,13 @@
+## 1.3.0 (10/03/2017)
+
+Features:
+  - Improve affected user handling to let you specify all Raygun parameters, identifier, email, first name, full name and uuid. See [README.md](https://github.com/MindscapeHQ/raygun4ruby#affected-user-tracking) for details
+  - Pass a user object as the third parameter to `Raygun.track_exception` to have affected user tracking for manually tracked exceptions, see the above link for more information on configuring this
+  - If the exception instance responds to `:raygun_custom_data` that method will be called and the return value merged into the `custom_data` hash sent to Raygun. For convenience a `Raygun::Error` class is provided that takes this custom data as a second argument
+  - Allowed `Configuration.custom_data` to be set to a proc to allow a global custom data hook for all exceptions. It is passed as arguments the exception and the environment hash
+  - Added `Configuration.debug` to enable logging the reason why an exception was not reported
+
 ## 1.2.1 (09/03/2017)
 
 Bugfixes:
   - dup input hashes before applying whitelist filtering, previously this was modifying the contents of `action_dispatch.request.parameters`