Updated to 0.14.1

CHANGELOG.md

@@ -1,55 +1,61 @@
-# v0.14.0
+# v0.14.1
+
+  * Enhancements
+    * Using the Dict Protocol for accessing data
 
-* Enhancements
-  * The `Joken.Config` behaviour handles the configuration of the secret_key, algorithm, encode and decode functions, as well as functions for adding and validating claims 
-  * Add `options` parameter to `Joken.Token.decode`
-  * Add `options` parameter to `Joken.decode`
-  * Removed `:none` algorithm completely
+# v0.14.0
 
-* Breaking
-  * `Joken.Codec` is replaced by `Joken.Config`. 
-  * `json_module` in config is replaced by `config_module`. 
-  * `algorithm` and `secret_key` in config is replaced by implementing the `algorithm` and `secret_key` functions on `Joken.Config`. 
-  * `Joken.Token.encode` now has a signature of `(joken_config, payload)` since the algorithm and secret key are defined inside of the passed in `joken_config` module.
-  * `Joken.Token.decode` now has a signature of `(joken_config, jwt, options \\ [])` since the algorithm and secret key are defined inside of the passed in `joken_config` module.
+  * Enhancements
+    * The `Joken.Config` behaviour handles the configuration of the secret_key, algorithm, encode and decode functions, as well as functions for adding and validating claims 
+    * Add `options` parameter to `Joken.Token.decode`
+    * Add `options` parameter to `Joken.decode`
+    * Removed `:none` algorithm completely
+
+  * Breaking
+    * `Joken.Codec` is replaced by `Joken.Config`. 
+    * `json_module` in config is replaced by `config_module`. 
+    * `algorithm` and `secret_key` in config is replaced by implementing the `algorithm` and `secret_key` functions on `Joken.Config`. 
+    * `Joken.Token.encode` now has a signature of `(joken_config, payload)` since the algorithm and secret key are defined inside of the passed in `joken_config` module.
+    * `Joken.Token.decode` now has a signature of `(joken_config, jwt, options \\ [])` since the algorithm and secret key are defined inside of the passed in `joken_config` module.
 
 # v0.13.1
+
   * Enhancements
     * Checking to make sure signature is on token unless `:none` is passed as the algorithm
 
 # v0.13.0
 
-* Enhancements
-  * Validating iat claim
-  * Verifying signature before getting the data
+  * Enhancements
+    * Validating iat claim
+    * Verifying signature before getting the data
 
 # v0.12.0
 
-* Enhancements
-  * Signature is now verified just from the header and payload strings.
-  * Added `decode_secret_key?` parameter
+  * Enhancements
+    * Signature is now verified just from the header and payload strings.
+    * Added `decode_secret_key?` parameter
 
 # v0.11.0
 
-* Enhancements
-  * `Joken` module now looks more like old API from 0.8 with the exception that it reads configuration from a :joken config block.
-  * For security reasons, now using the configured algorithm for checking signature instead of the one specified in the header.
-  * Added algorithm paramter to `Joken.Token.decode` to be used when verifying signatures
+  * Enhancements
+    * `Joken` module now looks more like old API from 0.8 with the exception that it reads configuration from a :joken config block.
+    * For security reasons, now using the configured algorithm for checking signature instead of the one specified in the header.
+    * Added algorithm paramter to `Joken.Token.decode` to be used when verifying signatures
 
 # v0.10.1
 
-* Enhancements
-  * Fixed documentation typos
-  * Joken now uses an Agent instead of implementing GenServer
+  * Enhancements
+    * Fixed documentation typos
+    * Joken now uses an Agent instead of implementing GenServer
 
 
 # v0.10.0
 
-* Enhancements
-  * No longer has a dependency on Timex or JSX
-  * Can now use any json library as long as you implement the behaviour, `Joken.Codec`
-  * Joken module is now a GenServer
-  * secret_key, algorithm, and json_module are now configured when the starting Joken module
+  * Enhancements
+    * No longer has a dependency on Timex or JSX
+    * Can now use any json library as long as you implement the behaviour, `Joken.Codec`
+    * Joken module is now a GenServer
+    * secret_key, algorithm, and json_module are now configured when the starting Joken module
 
-* Breaking
-  * `Joken.encode(payload, secret, algorithm, claims)` is now `Joken.encode(pid, payload, claims)` and `Joken.decode(token, secret, claims)` is now `Joken.decode(pid, token, claims)`. `secret_key` and `algorithm` are now configured along with `json_module` when starting the Joken module via any of the `Joken.start_link` functions. You could also use the `Joken.Token` module directly instead which isn't a GenServer and allows you to put in all of the parameters needed whenever you call encode or decode. 
+  * Breaking
+    * `Joken.encode(payload, secret, algorithm, claims)` is now `Joken.encode(pid, payload, claims)` and `Joken.decode(token, secret, claims)` is now `Joken.decode(pid, token, claims)`. `secret_key` and `algorithm` are now configured along with `json_module` when starting the Joken module via any of the `Joken.start_link` functions. You could also use the `Joken.Token` module directly instead which isn't a GenServer and allows you to put in all of the parameters needed whenever you call encode or decode. 

mix.exs

@@ -3,7 +3,7 @@ defmodule Joken.Mixfile do
 
   def project do
     [app: :joken,
-     version: "0.14.0",
+     version: "0.14.1",
      elixir: "~> 1.0.0",
      description: description,
      package: package,