CHANGELOG.md in dato-0.7.15 vs CHANGELOG.md in dato-0.7.16

@@ -1,5 +1,9 @@
+# 0.7.16
+
+Fixes bug when launching `dato dump --watch` together with the `environment` option.
+
 # 0.7.13
 
 Add option to pass a project's environment:
 
 ```ruby
@@ -32,51 +36,51 @@
 
 Find more info [on the documentation](https://www.datocms.com/docs/content-management-api/resources/item/create).
 
 # 0.7.11 (not released)
 
-* Updated specs cassettes after `appeareance -> appearance` typo fix
-* Some style changes
+- Updated specs cassettes after `appeareance -> appearance` typo fix
+- Some style changes
 
 # 0.7.10
 
-* Fixed SEO title retrieval. Now it fallbacks to default SEO title is item title is blank
+- Fixed SEO title retrieval. Now it fallbacks to default SEO title is item title is blank
 
 # 0.7.9
 
-* Added new attributes to uploads
+- Added new attributes to uploads
 
 # 0.7.0
 
-* Real-time events are now much more granular and the gem avoids downloading all the content every time a change occurs
+- Real-time events are now much more granular and the gem avoids downloading all the content every time a change occurs
 
 # 0.6.18
 
-* Fixed regression where you could no longer access items' item type
+- Fixed regression where you could no longer access items' item type
 
 # 0.6.15
 
-* Handle `429 Too Many Requests` responses from API
+- Handle `429 Too Many Requests` responses from API
 
 # 0.6.12
 
-* Allow empty responses from server
+- Allow empty responses from server
 
 # 0.6.10
 
-* Introduced `.meta` on `Dato::Local::Item` to fetch all meta information about the records
+- Introduced `.meta` on `Dato::Local::Item` to fetch all meta information about the records
 
 # 0.6.5
 
-* The `.seo_meta_tags` method now generates fallback titles based on the model field title
+- The `.seo_meta_tags` method now generates fallback titles based on the model field title
 
 # v0.6.2
 
 Moved `json_schema` as runtime dependency
 
 # v0.6.1
 
-The big change is that the methods the client makes available are  generated at runtime based on the [JSON Schema of our CMA](https://www.datocms.com/content-management-api/). This means any new API endpoint — or changes to existing ones — will instantly be reflected to the client, without the need to upgrade to the latest client version.
+The big change is that the methods the client makes available are generated at runtime based on the [JSON Schema of our CMA](https://www.datocms.com/content-management-api/). This means any new API endpoint — or changes to existing ones — will instantly be reflected to the client, without the need to upgrade to the latest client version.
 
 We also added a new `deserialize_response` option to every call, that you can use if you want to retrieve the exact payload the DatoCMS returns:
 
 ```ruby
 require "dato"