UNPKG

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