v0.26.0

• Changed how Mosca is configured
  #200
• Fail authentication without username & password
• Changed how data is stored inside leveldb in embedded mode, with
  simplified TTL handling
• Updated dependencies

v0.25.1

• Fixed a security bug in the will authorization handling.

v0.25.0

• Fixed problematic bug with MongoDB that could lead to message loss.
• Updated dependencies.

v0.24.1

• Fix for RabbitMQ support
  #189.

v0.24.0

• Updated dependencies (Redis, MongoDB, ecc)
• Close clients with the same clientId even if they are connected to another Mosca
  #182
  #92.

v0.23.2

• Fixed offline mode for Redis
  #128.

v0.23.1

• Fixed JSON-based authorizer to support generic 'authorize all'
  catchall.

v0.23.0

• Use an unique id (shortid) for server-level messageId.
  #176.
• Removed node-uuid in favor of shortid.
• Bumped browserify to v4.2.0.
• Allow persistence.factory key to be a string in the configuration/options
  #171.
• Do not store inflight packets on disconnection
  #175.
• Send suback 0x80 if a subscription fails
  #170.
• Moved pre-commit into devDependencies.
  #177.

Thanks to Morgan Cheng for all the work
spent to make Mosca rock solid on Redis.

v0.22.0

• Redis packets TTL (offline).
  #164.
• Require redis > 2.6.
• Added server#authorizeForward method
  #168.
• Topics are no longer normalised from e.g a///topic to a/topic. This
  matches the behaviour as clarified by the Oasis MQTT spec. This will
  lead to unexpected behaviour if you were using topics of this form.

v0.21.9

• Really fixed LevelUp and Memory persistence for offline messages, previously
  only one offline message per second was allowed
  #160.
• Bumped levelup, memdown, level-ttl dependencies.