UNPKG

6.58 kBMarkdownView Raw
1# 2.8.0 (2021-11-25)
2- [FIXED] Corrected `user-agent` header on requests.
3- [FIXED] Restore of shallow backups created with versions <=2.4.2.
4- [IMPROVED] Added quiet option to backup and restore to suppress batch messages.
5- [IMPROVED] Added a preflight check for restore function to make sure that a target database is new and empty.
6- [IMPROVED] Added handling for errors reading log file.
7- [IMPROVED] Split changes spooling to improve reliability on databases with
8 millions of documents.
9- [UPGRADED] `@ibm-cloud/cloudant`, `commander` and `debug` dependencies.
10
11# 2.7.0 (2021-09-14)
12- [UPGRADED] Cloudant client dependency from `@cloudant/cloudant` to `@ibm-cloud/cloudant`.
13
14# 2.6.2 (2021-08-27)
15- [FIXED] `Invalid document ID: _bulk_get` error when using `@cloudant/cloudant`
16 version `4.5.0`.
17- [UPGRADED] Upgraded `@cloudant/cloudant` dependency to version `4.5.0`.
18- [NOTE] Updated minimum supported engine to Node.js 12 `erbium` LTS.
19
20# 2.6.1 (2021-06-23)
21- [FIXED] Async queue pause/resume behaviour to avoid exhausting listener handles.
22- [UPGRADED] Upgraded `@cloudant/cloudant` dependency to version `4.4.0`.
23
24# 2.6.0 (2020-09-22)
25- [FIXED] Invalid parameters error when using shallow mode.
26- [UPGRADED] Upgraded `@cloudant/cloudant` dependency to version `4.3.0`.
27- [NOTE] Updated minimum supported engine to Node.js 10 `dubnium` LTS.
28
29# 2.5.2 (2020-03-02)
30- [FIXED] Issue with compatibility with Nano 8.2.0.
31
32# 2.5.1 (2019-12-06)
33- [FIXED] Issue with incorrect handling of percent-encoded user info characters
34 via @cloudant/cloudant dependency.
35- [UPGRADED] Upgraded @cloudant/cloudant dependency to minimum version 4.2.3
36- [IMPROVED] Added documentation around encoding of characters in the user info
37 subcomponent of the URL.
38
39# 2.5.0 (2019-10-24)
40- [UPGRADED] Upgraded @cloudant/cloudant dependency to version 4.2.2.
41- [NOTE] Updated minimum supported engine to Node.js 8 “Carbon” LTS.
42
43# 2.4.2 (2019-08-20)
44
45- [FIXED] Preserve document revisions in shallow backup.
46- [UPGRADED] Upgraded commander dependency to version 3.0.0.
47
48# 2.4.1 (2019-06-18)
49
50- [FIXED] Removed inadvertent npm-cli-login dependency.
51- [UPGRADED] Upgraded @cloudant/cloudant dependency to version 4.1.1.
52- [UPGRADED] Upgraded async dependency to version 3.0.1.
53
54# 2.4.0 (2019-03-15)
55
56- [NEW] Added request timeout option. Set via env var `COUCH_REQUEST_TIMEOUT`,
57 as CLI option `--request-timeout`, or programmatically via
58 `options.requestTimeout`.
59- [IMPROVED] Replaced usages of Node.js legacy URL API. Note this changes some
60 URL validation error messages.
61- [IMPROVED] Documentation, help text and log warnings for invalid options in
62 "shallow" mode.
63- [UPGRADED] Moved nodejs-cloudant dependency to 4.x.x.
64
65# 2.3.1 (2018-06-15)
66
67- [FIXED] Concurrent database backups use the same default log file.
68- [FIXED] IAM token URL override option.
69
70# 2.3.0 (2018-05-22)
71
72- [NEW] Check for database existence before starting backup. This provides for
73 better error messages for existence, authentication, and `_bulk_get` problems.
74- [FIXED] Intermittent issues with multiple callbacks, particularly noticeable
75 when using Node.js 10.
76- [FIXED] Issue where a success message could confusingly be output after a
77 fatal error.
78- [UPGRADED] Increased nodejs-cloudant dependency minimum to 2.2.x.
79
80# 2.2.0 (2018-03-06)
81
82- [FIXED] An issue where the `_changes` response stream doesn't get correctly
83 decompressed.
84- [FIXED] Prevent duplicate execution of backup error callbacks.
85- [NOTE] Update engines in preparation for Node.js 4 “Argon” end-of-life.
86
87# 2.1.0 (2018-02-20)
88
89- [NEW] Added API for upcoming IBM Cloud Identity and Access Management support
90 for Cloudant on IBM Cloud. Note: IAM API key support is not yet enabled in the
91 service.
92- [IMPROVED] Enhanced resilience of backup and restore processes by enabling the
93 nodejs-cloudant retry plugin.
94- [IMPROVED] Added URL validation for presence of host and database elements.
95- [UPGRADED] Increased nodejs-cloudant dependency to 2.x.
96
97# 2.0.1 (2018-01-11)
98
99- [NEW] Changed to use nodejs-cloudant for database requests.
100- [IMPROVED] Added compression to restore process requests.
101- [FIXED] An unhandled `readstream.destroy is not a function` error when trying
102 to terminate a restore process that encountered an error.
103- [UPGRADED] Increased debug dependency to 3.0.x.
104
105# 2.0.0 (2017-07-04)
106
107- [NEW] Moved to https://github.com/cloudant/couchbackup repository.
108- [NEW] Validate backup/restore options.
109- [NEW] Add User-Agent header to all requests.
110- [NEW] Added unique CLI exit codes for known error conditions.
111- [NEW] API for using as library that is more Node.js-like.
112- [NEW] Added `changes` event for each batch spooled from the changes feed.
113- [BREAKING CHANGE] The --buffer option is now --buffer-size.
114- [BREAKING CHANGE] The `writeerror` event is now just `error`.
115- [BREAKING CHANGE] The `writecomplete` event is now `finished`.
116- [BREAKING CHANGE] For restoring, the `written` event is now `restored`.
117- [REMOVED] Removed legacy 1.x API.
118- [IMPROVED] Verify database supports `/_bulk_get` endpoint prior to running backup.
119- [IMPROVED] Existence of the restore destination database is checked before
120 starting the restore process.
121- [IMPROVED] Added compression for backup HTTP responses, where supported by the
122 server.
123- [IMPROVED] Added HTTP persistent connection pools corresponding to the backup
124 parallelism.
125- [IMPROVED] Better error handling in couchrestore when remote database
126 cannot be written to.
127- [IMPROVED] Validate HTTP responses when restoring a database.
128- [IMPROVED] Aborts backup and restore processes for known irrecoverable errors.
129- [IMPROVED] Retry restore batches on transient errors.
130- [FIXED] An issue where the process could exit before the backup content was
131 completely flushed to the destination stream.
132- [FIXED] An issue where back pressure on the output stream was ignored
133 potentially resulting in the backup process running out of memory.
134- [FIXED] An issue where the log entry could be written for a batch before the
135 batch was written to the backup file.
136- [FIXED] An issue where a restore of a resumed backup might not complete due to
137 incomplete JSON entries in the backup file.
138- [FIXED] An issue where an empty batch could be written to the backup file.
139- [FIXED] An issue where the restore-time buffer size was ignored.
140- [FIXED] Ensure body 'rows' key exists before performing shallow backup.
141- [FIXED] An issue where write errors were not correctly reported.
142- [FIXED] An issue where couchbackup would attempt to write to an
143 invalid output file.
144
\No newline at end of file