Skip to content

Release 39.0.0

Choose a tag to compare

@github-actions github-actions released this 04 Oct 03:55
· 40 commits to main since this release
Immutable release. Only release title and notes can be modified.
39.0.0
709a2c8
  • 💔 useMWG can now only be set in the ExifTool constructor. read(), readRaw(), write(), and editTags() no longer accept it, and DefaultReadTaskOptions, DefaultReadRawTaskOptions, DefaultWriteTaskOptions, and WriteTaskOptionFields no longer include it. ExifTool never unloads MWG once a command loads it, so the per-call option gave wrong results on reused ExifTool processes: a useMWG: false read returned MWG tags if its process had already served a useMWG: true read or write, and a useMWG: true call made later calls on its process return MWG tags. Passing a useMWG that differs from the instance's now rejects. To use both, create two ExifTool instances.

  • 🐞 On a useMWG: true instance, rewriteAllTags(), extractThumbnail(), extractPreview(), extractJpgFromRaw(), extractBinaryTag(), extractBinaryTagToBuffer(), version(), and TagDescriptions now also send -use MWG. Before, they ran with MWG only if their ExifTool process had already served a read or write. For rewriteAllTags(), this matters because MWG's strict mode skips non-standard EXIF, IPTC, and XMP when copying tags. Custom enqueueTask() tasks can pass exiftool.options to the ExifToolTask constructor to do the same.

  • 🐞 On a useMWG: false instance, a command that may load MWG anyway, by referencing an MWG: tag (like a write() key of "MWG:Description") or by passing -use MWG, an -@ argument file, or a -p format file in readArgs or writeArgs, now retires its ExifTool process afterward, so later commands don't get MWG tags. batch-cluster starts at most one new process per minDelayBetweenSpawnMillis (1.5 seconds by default).

  • 🐞 TagDescriptions now throws if language isn't a language code like de or zh_cn. language is part of the disk cache filename, so a value like "../../../x" made it read and write x.json outside cacheDir.

  • 🐞 If synchronous disposal (using) hits disposalTimeoutMs and the forceful child process cleanup it then requests fails, the error is now logged instead of escaping as an unhandled rejection, which terminates Node.js by default.

  • 📦 Updated to ESLint 10 and enabled typescript-eslint's type-checked rules, plus rules from eslint-plugin-n, eslint-plugin-regexp, eslint-plugin-redos, eslint-plugin-mocha, and eslint-plugin-chai-friendly. None of the resulting fixes change runtime behavior. Editors now suggest ThumbnailImage, PreviewImage, and JpgFromRaw for PreviewTag, and tag names for deleteAllTags()'s retain option.

Full Changelog: 38.3.0...39.0.0