CHANGELOG.md in timber-2.6.2 vs CHANGELOG.md in timber-3.0.0

@@ -5,9 +5,18 @@
 The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/)
 and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html).
 
 ## [Unreleased]
 
+### Changed
+
+  - Timber's Rails integration has been moved to the optional `timber_rails` gem: https://github.com/timberio/timber-ruby-rails
+  - Timber's Rack integration has been moved to the optional `timber_rack` gem: https://github.com/timberio/timber-ruby-rack
+  - Custom events are no longer nested under the `custom.event` key, events are now merged into the root docoment.
+  - Custom contexts are no longer nested under the `context.custom` key, contexts are not part of the top-level `context` document.
+  - The Timber JSON schema (`$shema` key) was dropped since the Timber.io service no longer requires a strict schema (structured data in any shape is accepted).
+  - `Timber::LogDevices::HTTP#initialize` now takes a second `source_id` parameter. Timber's new API keys are no longer Timber source specific and therefore require a `source_id` to be specificed. Ex: `Timber::LogDevices::HTTP.new('api_key', 'source_id')`.
+
 ## [2.6.2] - 2018-10-17
 
 ### Fixed
 
   - Fixes an issue where logging without specifying data would raise an error