NeahOpti/node_modules/libmime/CHANGELOG.md

Changelog

5.3.6 (2024-11-29)

Bug Fixes

• deps: Bumped libqp to fix issue with missing whitespace (1137a9f)

5.3.5 (2024-04-12)

Bug Fixes

• deps: Bumped deps (0477e98)

5.3.4 (2024-02-23)

Bug Fixes

• deploy: fixed git repo url (0f3e5f4)
• deploy: fixed git repo url (4d584ad)

5.3.3 (2024-02-23)

Bug Fixes

• deploy: fixed git repo url (f8f788f)

5.3.2 (2024-02-23)

Bug Fixes

• deploy: fixed git repo url (2161a43)

5.3.1 (2024-02-23)

Bug Fixes

• deploy: include package-lock.json (8363bf4)

5.3.0 (2024-02-23)

Features

• deploy: added autopublish (3e8109f)

v5.2.1 2023-01-27

• Fix base64 encoding for emoji bytes in encoded words

v5.2.0 2022-12-08

• Bumped libqp to get rid of new Buffer warnings

v5.1.0 2022-04-28

• Bumped deps
• Removed Travis config
• Added Github actions file to run tests

v5.0.0 2020-07-22

• Removed optional node-iconv support
• Bumped dependencies
• Updated Travis test matrix, dropped Node 8

v4.2.1 2019-10-28

• Replace jconv with more recent encoding-japanese

v4.2.0 2019-10-28

• Use jconv module to parse ISO-2022-JP by default

v4.1.4 2019-10-28

• decodeWords should also decode empty content part WeiAnAn
• fix decode base64 ending with = WeiAnAn

v4.1.0 2019-05-01

• Experimental support for node-iconv

v4.0.1 2018-07-24

• Maintenance release. Bumped deps

v4.0.0 2018-06-11

• Refactored decoding of mime encoded words and parameter continuation strings

v3.0.0 2016-12-08

• Updated encoded-word generation. Previously a minimal value was encoded, so it was possible to have multiple encoded words in a string separated by non encoded-words. This was an issue with some webmail clients that stripped out the non-encoded parts between encoded-words so the updated method uses wide match by encoding from the first word with unicode characters to the last word. "a =?b?= c =?d?= e" -> "a =?bcd?= e"

v2.1.3 2016-12-08

• Revert dot as a special symbol

v2.1.2 2016-11-21

• Quote special symbols as defined in RFC (surajwy)

v2.1.1 2016-11-15

• Fixed issue with special symbols in attachment filenames

v2.1.0 2016-07-24

• Changed handling of base64 encoded mime words where multiple words are joined together if possible. This fixes issues with multi byte characters getting split into different mime words (against the RFC but occurs)

v2.0.3 2016-02-29

• Fixed an issue with rfc2231 filenames

v2.0.2 2016-02-11

• Fixed an issue with base64 mime words encoding

v2.0.1 2016-02-11

• Fix base64 mime-word encoding. Final string length was calculated invalidly

v2.0.0 2016-01-04

• Replaced jshint with eslint
• Refactored file structure

v1.2.1 2015-10-05

Added support for emojis in header params (eg. filenames)

v1.2.0 2015-10-05

Added support for emojis in header params (eg. filenames)

v1.1.0 2015-09-24

Updated encoded word encoding with quoted printable, should be more like required in https://tools.ietf.org/html/rfc2047#section-5

v1.0.0 2015-04-15

Changed versioning scheme to use 1.x instead of 0.x versions. Bumped dependency versions, no actual code changes.

v0.1.7 2015-01-19

Updated unicode filename handling – only revert to parameter continuation if the value actually includes non-ascii characters or is too long. Previously filenames were encoded if they included anything besides letters, numbers, dot or space.

v0.1.6 2014-10-25

Fixed an issue with encodeWords where a trailing space was invalidly included in a word if the word ended with an non-ascii character.

v0.1.5 2014-09-12

Do not use quotes for continuation encoded filename parts. Fixes an issue with Gmail where the Gmail webmail keeps the charset as part of the filename.