CHANGELOG.md in batch-loader-0.3.0 vs CHANGELOG.md in batch-loader-1.0.0

@@ -6,12 +6,52 @@
 one of the following labels: `Added`, `Changed`, `Deprecated`,
 `Removed`, `Fixed`, `Security`. We also use [Semantic Versioning](http://semver.org)
 to manage the versions of this gem so
 that you can set version constraints properly.
 
-#### [Unreleased](https://github.com/exAspArk/batch-loader/compare/v0.3.0...HEAD)
+#### [Unreleased](https://github.com/exAspArk/batch-loader/compare/v1.0.0...HEAD)
 
 * WIP
+
+#### [v1.0.0](https://github.com/exAspArk/batch-loader/compare/v0.3.0...v1.0.0) – 2017-08-21
+
+* `Removed`: `BatchLoader.sync!` and `BatchLoader#sync`. Now syncing is done implicitly when you call any method on the lazy object.
+
+Before:
+
+```ruby
+def load_user(user_id)
+  BatchLoader.for(user_id).batch { ... }
+end
+
+users = [load_user(1), load_user(2), load_user(3)]
+puts BatchLoader.sync!(users) # or users.map!(&:sync)
+```
+
+After:
+
+```ruby
+users = [load_user(1), load_user(2), load_user(3)]
+puts users
+```
+
+* `Removed`: `BatchLoader#load`. Use `loader` lambda instead:
+
+Before:
+
+```ruby
+BatchLoader.for(user_id).batch do |user_ids, batch_loader|
+  user_ids.each { |user_id| batch_loader.load(user_id, user_id) }
+end
+```
+
+After:
+
+```ruby
+BatchLoader.for(user_id).batch do |user_ids, loader|
+  user_ids.each { |user_id| loader.call(user_id, user_id) }
+end
+```
 
 #### [v0.3.0](https://github.com/exAspArk/batch-loader/compare/v0.2.0...v0.3.0) – 2017-08-03
 
 * `Added`: `BatchLoader::Executor.clear_current` to clear cache manually.
 * `Added`: tests and description how to use with GraphQL.