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