exiftool-vendored/CHANGELOG.md

Efficient, cross-platform access to ExifTool

# Changelog/Versioning

## Versioning

Providing the flexibility to reversion the API or UPDATE version slots as
features or bugfixes arise and using ExifTool's version number is at odds with
each other, so this library follows [Semver](https://semver.org/), and the
vendored versions of ExifTool match the version that they vendor.

### The `MAJOR` or `API` version is incremented for

- 💔 Non-backward-compatible API changes
- 🏚️ [End of life](https://github.com/nodejs/release#release-schedule) versions of Node.js are dropped from the build matrix

### The `MINOR` or `UPDATE` version is incremented for

- 🌱 New releases of ExifTool
- 🔥 Security updates
- ✨ Backwards-compatible features

### The `PATCH` version is incremented for

- 🐞 Backwards-compatible bug fixes
- 📦 Minor packaging changes

## Version history

### v30.2.0

- ✨ Enhanced `StrEnum` with iterator support and JSDoc

### v30.1.0

- 🌱 Upgraded ExifTool to version [13.30](https://exiftool.org/history.html#13.30).

- 🐞 Fixed `ExifToolVersion` to be a `string`. Prior versions used `exiftool`'s JSON representation, which rendered a numeric float. This caused versions like "12.3" and "12.30" to appear identical. We now preserve the exact version string to enable proper version comparisons.

- ✨ Added **partial date support** for `ExifDate` class. XMP date tags (like `XMP:CreateDate`, `XMP:MetadataDate`) now support:

  - **Year-only dates**: `1980` (numeric) or `"1980"` (string)
  - **Year-month dates**: `"1980:08"` (EXIF format) or `"1980-08"` (ISO format)
  - **Full dates**: `"1980:08:13"` (unchanged)

- ✨ Enhanced `ExifDate` with type-safe predicates:

  - `isYearOnly()`: Returns `true` for year-only dates with type narrowing
  - `isYearMonth()`: Returns `true` for year-month dates with type narrowing
  - `isFullDate()`: Returns `true` for complete dates with type narrowing
  - `isPartial()`: Returns `true` for year-only or year-month dates

- ✨ Added compositional TypeScript interfaces:

  - `ExifDateYearOnly`: `{year: number}`
  - `ExifDateYearMonth extends ExifDateYearOnly`: `{year: number, month: number}`
  - `ExifDateFull extends ExifDateYearMonth`: `{year: number, month: number, day: number}`

- ✨ Enhanced `WriteTags` interface with group-prefixed tag support:

  - `"XMP:CreateDate"`, `"XMP:MetadataDate"`, etc. accept partial dates
  - `"EXIF:CreateDate"`, etc. require full dates (type-safe distinction)

- 📦 Docs are now automatically updated via [GitHub Actions](https://github.com/photostructure/exiftool-vendored.js/actions/workflows/docs.yml)

- 📦 Added comprehensive test coverage (47 new tests) for partial date functionality

- 📦 Upgrade to batch-cluster [v14.0.0](https://github.com/photostructure/batch-cluster.js/releases/tag/v14.0.0) which removes the requirement for `procps` on most linux distributions.

### v30.0.0

- 💔 Dropped support for Node v18, whose End-of-Life was 2025-04-30.

- 🌱 Upgraded ExifTool to version [13.29](https://exiftool.org/history.html#13.29).

- ✨ Added new `TagNames` string enumeration with the most popular 2,500(ish) tag field names that is automatically updated by `mktags`. As a reminder: the `Tags` interface _is not comprehensive_. If we're missing any of your favorite fields, open an issue with an attached example media file and I look into promoting it to a "guaranteed" status (like we've done with several hundred fields already).

- 📦 Renamed the `.tz` field in `Tags` to `.zone`. Note that for the next few releases, `.tz` will be kept, but marked as deprecated. After doing a bit of research, it turns out the correct term for identifiers like `America/Los_Angeles` within the IANA Time Zone Database is "zone." The "tz" term commonly refers to the entire Time Zone Database, or "tz database" (also called tzdata or zoneinfo).

- ✨ Updating to new versions of ExifTool is now fully automated via GitHub Actions.

### v29.3.0

- 🌱 Upgraded ExifTool to version [13.26](https://exiftool.org/history.html#13.26).

- ✨ Added support for [keepUTCTime](https://exiftool.org/ExifTool.html#KeepUTCTime) to ExifToolOptions. This is a new ExifTool feature specifically for unixtime-encoded datetimes, but seems to be rarely applicable as unixtime is not a valid encoding format for most datetime tags.

### v29.2.0

- 🌱 Upgraded ExifTool to version [13.25](https://exiftool.org/history.html#13.25).

- ✨ [ExifTool.write](https://photostructure.github.io/exiftool-vendored.js/classes/ExifTool.html#write) now supports `boolean` field values. Thanks for the [suggestion](https://github.com/photostructure/exiftool-vendored.js/issues/228), [Kira-Kitsune](https://github.com/Kira-Kitsune).

- 📦 Updated the default for [maxProcs](https://photostructure.github.io/exiftool-vendored.js/interfaces/ExifToolOptions.html#maxprocs) to use [availableParallelism](https://nodejs.org/api/os.html#osavailableparallelism) where available.

### v29.1.0

- 🌱 Upgraded ExifTool to version [13.17](https://exiftool.org/history.html#13.17). Note that this release includes **seventeen** ExifTool version bumps (from November 2024 through January 2025--Phil Harvey has been _busy_!). Although I haven't seen any breaking changes in the Tags generation or test suite with the new versions, please do your own validation.

- ✨ Thanks to [Mert](https://github.com/mertalev) for [adding forceWrite to binary tag extraction](https://github.com/photostructure/exiftool-vendored.js/pull/222).

- ✨ ExifTool's Geolocation feature seems to work around some obscure GPS encoding issues where the decimal sign gets ignored. This project now leverages that "corrected" GPS location by adopting the hemisphere signs, which seems to [fix this issue](https://github.com/immich-app/immich/issues/13053).

- 🐞 Removed `OffsetTime` from the list of Timezone offset tags we infer tz from. Thanks for the [heads-up](https://github.com/photostructure/exiftool-vendored.js/issues/220), [Carsten Otto](https://github.com/C-Otto)!

- 📦 Updated to the latest `eslint`, which required rewriting the config, and delinting the new nits

- 📦 Deleted most of the `prettier` config to accept their defaults. This created a huge [no-op commit](https://github.com/photostructure/exiftool-vendored.js/commit/622e8a814e22697c25efeb911215855753a97892) but now it's over.

### v29.0.0

- 💔/🐞/📦 ExifTool sometimes returns `boolean` values for some tags, like `SemanticStylePreset`, but uses "Yes" or "No" values for other tags, like `GPSValid` (TIL!). If the tag name ends in `Valid` and is truthy (1, true, "Yes") or falsy (0, false, "No"), we'll convert it to a boolean for you. Note that this is arguably a breaking API change, but it should be what you were already expecting (so is it a bug fix?). See the diff to the Tags interface in this version to verify what types have changed.

- 📦 Reduced `streamFlushMillis` to `10`. This reduced elapsed time for the full test suite by 2.5x on macOS and 3x on Windows, and drops the upper latency bound substantially. Note that this is at the risk of buffered stream collisions between tasks. The (extensive) test suite on Github Actions (whose virtual machines are notoriously slower than molasses) still runs solidly, but if you see internal errors, please open a Github issue and increase your `streamFlushMillis`.

- 💔 TypeScript now emits ES2022, which requires Node.js 18.

#### GPS improvements

- 🐞/📦 GPS Latitude and GPS Longitude values are now parsed from [DMS notation](<https://en.wikipedia.org/wiki/Degree_(angle)#Subdivisions>), which seems to avoid some incorrectly signed values in some file formats (especially for some problematic XMP exports, like from Apple Photos). Numeric GPSLatitude and GPSLongitude are still accepted: to avoid the new coordinates parsing code, restore `GPSLatitude` and `GPSLongitude` to the `ExifToolOptions.numericTags` array.

- 🐞/📦 If `ExifToolOptions.geolocation` is enabled, and `GeolocationPosition` exists, and we got numeric GPS coordinates, we will assume the hemisphere from GeolocationPosition, as that tag seems to correct for more conditions than GPS\*Ref values.

- 🐞/📦 If the encoded GPS location is invalid, all `GPS*` and `Geolocation*` metadata will be omitted from `ExifTool.readTags()`. Prior versions let some values (like `GPSCoordinates`) from invalid values slip by. A location is invalid if latitude and longitude are 0, out of bounds, either are unspecified.

- 🐞/📦 Reading and writing GPS latitude and GPS longitude values is surprisingly tricky, and could fail for some file formats due to inconsistent handling of negative values. Now, within `ExifTool.writeTags()`, we will automatically set `GPSLatitudeRef` and `GPSLongitudeRef` if lat/lon are provided but references are unspecified. More tests were added to verify this workaround. On reads, `GPSLatitudeRef` and `GPSLongitudeRef` will be backfilled to be correct. Note that they only return `"N" | "S" | "E" | "W"` now, rather than possibly being the full cardinal direction name.

- 🐞 If `ignoreZeroZeroLatLon` and `geolocation` were `true`, (0,0) location timezones could still be inferred in prior versions.

- 📦 GPS coordinates are now round to 6 decimal places (≈11cm precision). This exceeds consumer GPS accuracy while simplifying test assertions and reducing noise in comparisons. Previously storing full float precision added complexity without practical benefit.

### v28.8.0

**Important:** ExifTool versions use the format `NN.NN` and do not follow semantic versioning. The version from ExifTool will not parse correctly with the `semver` library (for the next 10 versions) since they are zero- padded.

- 🌱 Upgraded ExifTool to version [13.00](https://exiftool.org/history.html#13.00)

  **Note:** ExifTool version numbers increment by 0.01 and do not follow semantic versioning conventions. The changes between version 12.99 and 13.00 are minor updates without any known breaking changes.

- 📦 Added Node.js v23 to the build matrix.

### v28.7.0

- 🌱 ExifTool upgraded to version [12.99](https://exiftool.org/history.html#12.99)

### v28.6.0

- 🌱 ExifTool upgraded to version [12.97](https://exiftool.org/history.html#12.97)

- 📦 Fields in `Tags` sub-interfaces are correctly sorted

### v28.5.0

- 🐞/📦 Add new `ExifToolOptions.preferTimezoneInferenceFromGps` to prefer GPS timezones. See the jsdoc for details.

- 🐞 Support triple-deep IANA timezones, like `America/Indiana/Indianapolis`.

### v28.4.1

- 📦 The warning "Invalid GPSLatitude or GPSLongitude. Deleting geolocation tags" will only be added if `GPSLatitude` or `GPSLongitude` is non-null.

### v28.4.0

- ✨ Add workaround for abberant Nikon `TimeZone` encoding. Addresses [#215](https://github.com/photostructure/exiftool-vendored.js/issues/215). Set `ExifToolOptions.adjustTimeZoneIfDaylightSavings` to `() => undefined` to retain prior behavior.

### v28.3.1

- 🐞 Re-add +13:00 as a valid timezone offset. Addresses [#214](https://github.com/photostructure/exiftool-vendored.js/issues/214).

### v28.3.0

- 🌱 ExifTool upgraded to [v12.96](https://exiftool.org/history.html#12.96)

- ✨ Add support for timezone offset extraction from `TimeStamp`. Note that this is disabled by default to retain prior behavior (and due to me being chicken that this might break other random cameras). Addresses [#209](https://github.com/photostructure/exiftool-vendored.js/issues/209)

- ✨ [@bugfest](https://github.com/bugfest) improved write typings around `Struct`s. Thanks! See [#212](https://github.com/photostructure/exiftool-vendored.js/pull/212)

- 🐞 [@noahmorrison](https://github.com/noahmorrison) found and fixed an issue with `inferLikelyOffsetMinutes`. Thanks for the assist! See [#208](https://github.com/photostructure/exiftool-vendored.js/pull/208) for details.

- 📦/💔 Possible breaking change: several archane timezone offsets were removed from the `ValidTimezoneOffsets` array, to better address [#208](https://github.com/photostructure/exiftool-vendored.js/pull/208).

### v28.2.1

- 📦 Add `snyk-linux` to npmignore to fix [#200](https://github.com/photostructure/exiftool-vendored.js/issues/200)

### v28.2.0

- 🌱/✨/🐞 ExifTool upgraded to [v12.91](https://exiftool.org/history.html#12.91). Notably, the shebang line has changed from `/usr/bin/perl` to `/usr/bin/env perl`. The [exiftool-vendored.pl package](https://github.com/photostructure/exiftool-vendored.pl/blob/9606de60669da56908c472b8b964f7fd17784df8/update.sh#L24) works around [a new error from this shebang line](https://exiftool.org/forum/index.php?topic=16271.0).

### v28.1.0

- 📦 Add tests for [#187](https://github.com/photostructure/exiftool-vendored.js/issues/187)

- 📦 Export `ImageDataHashTag` interface

### v28.0.0

- 🌱/✨/🐞 ExifTool upgraded to [v12.89](https://exiftool.org/history.html#12.89). Notably, ExifTool on Windows is now using the "official" packaging. This should be equivalent to prior builds, as [exiftool-vendored.exe](https://github.com/photostructure/exiftool-vendored.exe) was already using Oliver Betz's perl launcher.

- 💔 Prior versions included `APP1Tags`, `APP4Tags`, `APP5Tags`, `APP6Tags`, `APP12Tags`, and `APP14Tags`. Unfortunately, due to field name duplications, fields could hop between these interfaces between versions. These have all been collapsed into a single new `APPTags`.

- ✨ Added support for [old Sony A7 UTC inference](https://github.com/photostructure/exiftool-vendored.js/issues/187). Thanks for the help, [Friso Smit](https://github.com/fwsmit)!

- ✨ Added support for [Android Motion Photos](https://github.com/photostructure/exiftool-vendored.js/issues/189). Thanks for the help, [Lukas](https://github.com/lukashass)!

- 📦 Updated `ReadTask` and `WriteTask` constructors to be public as well as the `.parse()` methods as a workaround for [#190](https://github.com/photostructure/exiftool-vendored.js/issues/190)

- 📦 Fought AND WON [a very obscure issue with Node v22.5.0](https://photostructure.com/coding/node-22-exit-handler-never-called/)

### v27.0.0

- 💔 `ExifToolOptions.struct` is now `"undef" | 0 | 1 | 2`. See
  [#184](https://github.com/photostructure/exiftool-vendored.js/issues/184)

- ✨ `ExifToolOptions` now includes `readArgs` and `writeArgs`, which can be
  specified both at `ExifTool` construction, as well as calls to `ExifTool.read`
  and `ExifTool.write`. The prior method signatures are deprecated.

### v26.2.0

- ✨ Support for all ExifTool `struct` modes (fixes [#184](https://github.com/photostructure/exiftool-vendored.js/issues/184)). See [ExifToolOptions.struct](https://photostructure.github.io/exiftool-vendored.js/interfaces/ExifToolOptions.html#struct) for details.

- 📦 Fix documentation to reference ExifTool.read() (fixes [#183](https://github.com/photostructure/exiftool-vendored.js/issues/183))

### v26.1.0

- 🌱/✨/🐞 ExifTool upgraded to [v12.85](https://exiftool.org/history.html#12.85). Notably, this addresses [reversed HEIC orientation](https://exiftool.org/forum/index.php?topic=15240.msg86229#msg86229).

- 🐞 Perhaps address [Perl not installed error](https://github.com/photostructure/exiftool-vendored.js/issues/182).

### v26.0.0

- 🌱/✨ ExifTool upgraded to [v12.84](https://exiftool.org/history.html#12.84)

- 📦 Support **disabling** `-ignoreMinorErrors` to work around shenanigans like [#181](https://github.com/photostructure/exiftool-vendored.js/issues/181). This is an optional field that defaults to prior behavior (enabled, which ignores minor errors, which is normally desired, _but has some side effects like fully reading tags that may be extremely long_). See [ExifToolOptions.ignoreMinorErrors](https://photostructure.github.io/exiftool-vendored.js/interfaces/ExifToolOptions.html#ignoreMinorErrors) for details.

- 📦 ExifTool on Windows was upgraded to Strawberry Perl 5.32.1

### v25.2.0

- 🌱/✨ ExifTool upgraded to [v12.82](https://exiftool.org/history.html#v12.82)

- 📦 Add support for `NODE_DEBUG=exiftool-vendored`

- 📦 Export `exiftoolPath()` so custom implementations can use it as a fallback
  (or default, and provide their own fallback)

### v25.1.0

- ✨ Added `retain` field to [`ExifTool.deleteAllTags`](https://photostructure.github.io/exiftool-vendored.js/classes/ExifTool.html#deleteAllTags) to address [#178](https://github.com/photostructure/exiftool-vendored.js/issues/178)

- 📦 Added jsdocs for many `Tag` interface types

- 📦 Expose `GeolocationTags` and `isGeolocationTag()`

- 📦 Add `FileTags.FileCreateDate` (only a thing on Windows)

### v25.0.0

- 🌱/✨ ExifTool upgraded to [v12.80](https://exiftool.org/history.html#v12.80), which **adds support for reverse-geo lookups** and [several other geolocation features](https://exiftool.org/geolocation.html)

- ✨ If no vendored version of `exiftool` is available, we'll try to make do with whatever is available in the `PATH`.

- ✨ `ExifToolOptions.exiftoolPath` can now be an `async` function

- ✨ Added [Geolocation](https://photostructure.github.io/exiftool-vendored.js/interfaces/GeolocationTags.html) Tags. These will only be available if `{geolocation: true}` is passed to the [ExifTool constructor](https://photostructure.github.io/exiftool-vendored.js/classes/ExifTool.html#constructor).

- 📦 Added support for `electron-forge`: [see the docs for details](https://photostructure.github.io/exiftool-vendored.js/#md:electron-forge-support).

### v24.6.0

- 🌱 ExifTool upgraded to [v12.78](https://exiftool.org/history.html#v12.78)

- 📦 Added [ExifTool.off](https://photostructure.github.io/exiftool-vendored.js/classes/ExifTool.html#off)

### v24.5.0

- 🌱 ExifTool upgraded to [v12.76](https://exiftool.org/history.html#v12.76). Note that an ARW file corrupting issue was found that's existed since v12.45.

- 📦 Updated dependencies, including new [batch-cluster v13](https://github.com/photostructure/batch-cluster.js/releases/tag/v13.0.0) 🍀

### v24.4.0

- 🌱 ExifTool upgraded to [v12.73](https://exiftool.org/history.html#v12.73).

- 📦 If the underlying Perl installation is invalid, throw an error. [See #168 for details.](https://github.com/photostructure/exiftool-vendored.js/issues/168)

### v24.3.0

- 🌱 ExifTool upgraded to [v12.72](https://exiftool.org/history.html#v12.72).

- 📦 Relax GPS latitude/longitude parser to handle invalid Ref values (a warning will be appended to the [Tags.warnings field](https://photostructure.github.io/exiftool-vendored.js/interfaces/Tags.html#warnings)). See [#165](https://github.com/photostructure/exiftool-vendored.js/issues/165).

### v24.2.0

- 🐞 If `perl` isn't installed in `/usr/bin`, feed the full path to `perl` (if we can find it) to `spawn` (rather than relying on the shell to use `$PATH`). This should address issues like [#163](https://github.com/photostructure/exiftool-vendored.js/issues/163)

### v24.1.0

- 📦 Relaxed `isWarning()` detection to be simply `/warning:/i`. v24.0.0 would throw errors when extracting binary thumbnails due to issues like "Warning: Ignored non-standard EXIF at TIFF-IFD0-JPEG-APP1-IFD0", which is decidedly a warning. `ExifTool.write` now leans (hard) on returning [`Tags.warnings`](https://photostructure.github.io/exiftool-vendored.js/interfaces/Tags.html#warnings) rather than throwing errors: **It is up to you to inspect `.warnings` and decide for your own usecase if the issue is exceptional**. See [issue #162](https://github.com/photostructure/exiftool-vendored.js/issues/162) for details.

### v24.0.0

- 💔 In the interests of reducing complexity, the `ExifToolOptions.isIgnorableError` predicate field was removed -- if this was used by anyone, please open an issue and we can talk about it.

- 💔 `ExifTool.write` now returns metadata describing how many files were unchanged, updated, or created, and **no longer throws errors** if the operation is a no-op or inputs are invalid. See [issue #162](https://github.com/photostructure/exiftool-vendored.js/issues/162) for details.

- ✨ `.warnings` are returned by `ExifTool.read` and `ExifTool.write` tasks if there are non-critical warnings emitted to `stderr` by ExifTool.

- 📦 Some fields in `Tags` were moved to more correct groups

- 📦 Refined `WriteTags` signature to omit `ExifToolTags` and `FileTags` fields.

- 📦 Added [`node:` prefix](https://nodejs.org/api/esm.html#node-imports) to Node.js module imports. This requires node v14.13, v16.0, or later.

### v23.7.0

- 📦 Added MWG `.HierarchicalKeywords` and `.Collections` to `Tags`

- 🐞/📦 `Rotation` was removed from the default set of `numericTags`, as it may
  be encoded as an EXIF orientation value, or a degree rotation, and it should
  be up to the application to figure it out.

### v23.6.0

- 📦 Added new option, `ignoreZeroZeroLatLon`, and **defaulted this new option
  to `true`**. Several camera manufacturers and image applications will write
  `0` to the `GPSLatitude` and `GPSLongitude` tags when they mean "unset"--but
  this can cause incorrect timezone inference. Set to `false` to retain prior
  code behavior.

- 📦 `Rotation` was added to the default set of `numericTags`, as it may be
  encoded as an EXIF orientation value. Prior builds could return Rotation
  values like `"Rotate 270 CW"`.

- 📦 `XMPTags.Notes` was added to `Tags`, used as an album description

- 🐞 Some `ExifToolOption`s were not passed from ExifTool into the ReadTask,
  which caused ReadTask to revert to defaults.

### v23.5.0

- 🌱 ExifTool upgraded to [v12.70](https://exiftool.org/history.html#v12.70). **🏆 Thanks for 20 years of updates, Phil Harvey! 🏆**

- 📦 `XMPTags.Album` was added to `Tags`

### v23.4.0

- 🌱 ExifTool upgraded to [v12.69](https://exiftool.org/history.html#v12.69)

- 📦 `ExifTool.read`: `ExifTime` now adopts the default zone extracted from
  the file. **This may result in different values for timestamps.**

- 📦 Updated dependencies

### v23.3.0

- 🐞 Restored datestamp parsing of `ResourceEvent.When`

### v23.2.0

- ✨ Timezone parsing improvements:

  - Added [`ExifToolOptions.inferTimezoneFromDatestampTags`](https://photostructure.github.io/exiftool-vendored.js/interfaces/ExifToolOptions.html#inferTimezoneFromDatestampTags).
  - Timezone inference from datestamps now skips over UTC values, as Google
    Takeout (and several other applications) may spuriously set "+00:00" to
    datestamps.
  - ReadTask.parse in prior versions had to scan all tags twice to set the
    timezone. Code was refactored to do this in a single pass.
  - Timezone extraction and normalization was improved.

- 📦 Add `creationDate` to [CapturedAtTagNames](https://photostructure.github.io/exiftool-vendored.js/variables/CapturedAtTagNames.html). [See PR#159](https://github.com/photostructure/exiftool-vendored.js/pull/159).

### v23.1.0

- 🌱 ExifTool upgraded to [v12.67](https://exiftool.org/history.html#v12.67)

- ✨ `ExifTime` now parses and stores timezone offsets if available. This resolves [issue
  #157](https://github.com/photostructure/exiftool-vendored.js/issues/157).
- 📦 `ExifDateTime`, `ExifTime`, and `ExifDate` are now [only allowed to try
  to parse keys that includes `date` or
  `time`](https://github.com/photostructure/exiftool-vendored.js/blob/ed7bf9eaea9b1d8ad234fb907953568219fc5bdb/src/ReadTask.ts#L389),
  which avoids incorrect parsing of tags like `MonthDayCreated` (which looks
  like `12:19`)

- 📦 Updated all dependencies, but only `devDependencies` were impacted.

### v23.0.0

- 🏚️ Dropped support for Node.js v16, which is [End-of-Life](https://nodejs.org/en/blog/announcements/nodejs16-eol).

- 💔/🐞 If `defaultVideosToUTC` is set to `true`, `read()` will now allow non-UTC
  timezones extractable from other tags to be assigned to `.tz`. Prior
  versions would simply force `.tz` to "UTC" for all videos, which wasn't
  great. Note that "UTC" is still used as the default timezone for all
  datestamps without explicit timezones, just as prior versions did. See [issue
  #156](https://github.com/photostructure/exiftool-vendored.js/issues/156) for
  details.

- 💔 `backfillTimezones` now defaults to `true`. Although this is likely to be
  what people expect, but know that this makes the assumption that all encoded
  times without an explicit offset share the same tz, which may not be correct
  (say, if you edit the image in a different timezone from when it was
  captured).

- 💔 If `backfillTimezones` is set to `false`, `ExifDateTime` will no longer
  use the current file's `.tz` as a default. Prior versions would inherit the
  file's `.tz`, which might be incorrect.

- 📦 `ExifDateTime` now includes an `.inferredZone` field, which may be useful
  in helping to determine how "trustworthy" the zone and actual datestamp
  value is.

### v22.2.3

- 🐞 Apply the v22.2.3 bugfix _even wider_ (just found a `SubSecTime` value of "01" in the wild, and it was happily parsed into today's date, oops).

### v22.2.2

- 🐞 Apply the v22.2.1 bugfix wider: we now reject parsing any date-ish or time-ish value that matches `/^0+$/`.

### v22.2.1

- 🐞 `ExifTime` now properly rejects invalid `SubSecTime`, `SubSecTimeOriginal`, ... values of "0" or "00".

### v22.2.0

- ✨ Add support for zone extraction from `ExifDateTime`, `ExifTime`, `number[]`, and `number` fields.

- 📦 Improve type signature of `extractTzOffsetFromTags`.

### v22.1.0

- 🌱 ExifTool upgraded to [v12.65](https://exiftool.org/history.html#v12.65)

- ✨ Add support for new `ImageDataHash` tag: [See the docs for details](https://photostructure.github.io/exiftool-vendored.js/interfaces/ExifToolOptions.html#imageHashType).

- 🐞 `perl` is checked for on non-windows machines at startup. This resolves [#152](https://github.com/photostructure/exiftool-vendored.js/issues/152). You can disable this with the [new `checkPerl` option](https://photostructure.github.io/exiftool-vendored.js/interfaces/ExifToolOptions.html#checkPerl).

### v22.0.0

- 🏚️ Drop support for Node 14, which EOL'ed 2023-04-30

- 🌱 ExifTool upgraded to [v12.62](https://exiftool.org/history.html#v12.62)

- 🐞 Fix exports for DefaultExifToolOptions and several other non-type values. Thanks for the [bug report, renambot!](https://github.com/photostructure/exiftool-vendored.js/issues/144)

### v21.5.1

- 📦 Avoid double-rendering of ImageDataMD5 (Thanks, Phil! See [forum post for details](https://exiftool.org/forum/index.php?topic=14706.msg79218#msg79218))

- 📦 Pull down new camera test images, rebuild Tags and docs

### v21.5.0

- ✨ Added support for ExifTool's [MWG Composite Tags](https://exiftool.org/TagNames/MWG.html). Set the new [`ExifToolOptions.useMWG`](https://photostructure.github.io/exiftool-vendored.js/interfaces/ExifToolOptions.html#useMWG) option to `true` to enable.

- ✨ Added support for ExifTool's new `ImageDataMD5` feature. Set the new [`ExifToolOptions.includeImageDataMD5`](https://photostructure.github.io/exiftool-vendored.js/interfaces/ExifToolOptions.html#includeImageDataMD5) option to `true` to enable.

- 📦 Extracted options-related code into modules to remove a couple circular
  dependencies. Exports should make this transparent to external clients.

### v21.4.0

- 🐞 Improved types from `ExifTool.readRaw()`. Thanks for the suggestion, [Silvio Brändle](https://github.com/photostructure/exiftool-vendored.js/issues/138)!

### v21.3.0

- 🌱 ExifTool upgraded to [v12.60](https://exiftool.org/history.html#v12.60)

- 📦 Replaced `Tags.tzSource` message `"from lat/lon"` to
  `"GPSLatitude/GPSLongitude"` to be more consistent with other timezone
  source messages.

### v21.2.0

- ✨ Implemented `ExifDateTime.plus()`. Added tests.

### v21.1.0

- 🐞 Negative GPSLatitude and GPSLongitude values are now supported for EXIF
  (like `.JPEG`), `.XMP`, and `.MIE` files. Thanks for the [bug
  report](https://github.com/photostructure/exiftool-vendored.js/issues/131),
  [Jason](https://github.com/contd), and the
  [solution](https://exiftool.org/forum/index.php?topic=14488.msg78082#msg78082),
  [Phil](https://exiftool.org/)!

- 🌱 ExifTool upgraded to [v12.56](https://exiftool.org/history.html#v12.56)

### v21.0.0

- 💔 `ExifDateTime.fromDateTime()` now takes an option hash as the second
  argument (instead of the second argument being `rawValue`)

- 🐞 `ExifDateTime.milliseconds` will now be `undefined` if the EXIF or ISO
  date string did not specify milliseconds, and will no longer render
  milliseconds if the `rawValue` did not include millisecond precision.

- 📦 EXIF and ISO dates without specified seconds or milliseconds are now allowed

- 📦 Switched `package.json` scripts from `yarn` to `npm`, as yarn@1 doesn't
  work with Node v22.5 and GitHub Actions.

### v20.0.0

- 💔 `ExifTool.write` took a generic that defaulted to `WriteTags`, but the type wasn't used for anything. I removed the generic typing, which may require consumers to change their code.

- 🌱 ExifTool upgraded to [v12.55](https://exiftool.org/history.html#v12.55)

- 📦 `npm run prettier` now re-organizes imports

- 📦 Updated dependencies, re-ran prettier, rebuilt tags, rebuilt docs

### v19.0.0

- 💔/🐞 [Fix #124](https://github.com/photostructure/exiftool-vendored.js/issues/124): Improved support for filenames with non-latin (a-z0-9) characters on Windows machines that weren't set to UTF-8. Thanks for the bug report and PR, [Jürg Rast](https://github.com/jrast)!

- 💔/🐞 ExifTool v12.54 has several new tags (see the diff) and now renders `GPSAltitude` with negative values when the altitude is below sea level.

- 🌱 ExifTool upgraded to [v12.54](https://exiftool.org/history.html#v12.54)

- 📦 Updated dependencies, re-ran prettier, rebuilt tags, rebuilt docs

- 📦 Node v19 added to the CI test matrix

### v18.6.0

- 🌱 ExifTool upgraded to [v12.50](https://exiftool.org/history.html#v12.50)

- 📦 Updated dependencies, rebuild tags and docs

### v18.5.0

- ✨ `ExifToolOptions` now supports an `ignorableError` predicate, used for characterizing errors as "ignorable". Defaults to ignoring the following styles of warnings:

  - `Warning: Duplicate MakerNoteUnknown tag in ExifIFD`
  - `Warning: ICC_Profile deleted. Image colors may be affected`

- 🐞 Only read operations are now retried. See [#119](https://github.com/photostructure/exiftool-vendored.js/issues/119#issuecomment-1299423164)

### v18.4.2

- 🐞 Date-time tags with exactly Common Epoch (`1970-01-01T00:00:00Z`) are no longer filtered as invalid. See [#118](https://github.com/photostructure/exiftool-vendored.js/issues/118) for details.

- 📦 Updated dependencies, rebuild tags and docs

### v18.4.1

- 🐞 The public export for `BinaryField` mistakenly exposed it being named
  `BinaryDataField`. The name of the export and the class are now both
  `BinaryField`.

### v18.4.0

- ✨ Binary fields are now parsed to a new `BinaryField` object which parses
  out the length of the binary field

- 🐞/📦 Added more required tag fields to `mktags`, including
  `SubSecModifyDate` (which fell off of the Tags.ts API in v18.3.0, oops!)

- 📦 `ExifTime` now retains the raw value to be consistent with `ExifDate` and `ExifDateTime`

### v18.3.0

- 🌱 ExifTool upgraded to [v12.49](https://exiftool.org/history.html#v12.49), which adds write support to WEBP and a bunch of other goodness

- 📦 Added new cameras to test image corpus, rebuilt tags and docs

- 📦 Updated dependencies

### v18.2.0

- ✨ Add support for alternative gps timezone lookup libraries. If you want to use `geo-tz` instead, use something like this:

```js
const geoTz = require("geo-tz");
const { ExifTool } = require("exiftool-vendored");
const exiftool = new ExifTool({
  geoToTz: (lat, lon) => geoTz.find(lat, lon)[0],
});
```

- ✨ If a timezone offset tag is present, _and_ GPS metadata can infer a timezone, _and_ they result in the same offset, `Tags.tz` will use the GPS zone name (like `America/Los_Angeles`).

- 🐞 We now only apply timezone offset defaults to tag values that are lacking in explicit offsets and are not always encoded in UTC.

- 📦 Timezone "normalization" to a single timezone is no longer applied--if a datetime tag has an offset, the ExifDateTime value should retain that offset value now. Use `ExifDateTime.setZone` if you want to normalize any instance.

- 📦 Restore `GPSPosition` to the default `numericTags` so all GPS lat/lon values are consistent.

### v18.1.0

- 📦 Switch from the abandoned `tz-lookup` package to [`@photostructure/tz-lookup`](https://github.com/photostructure/tz-lookup). Note that this uses an updated time zone geo database, so some time zone names and geo shapes have changed.

- 📦 The `GPSPosition` tag is no longer included in the default set of numeric tags, as this results in ExifTool returning two floats, whitespace-separated. Use `GPSLatitude` and `GPSLongitude` instead.

### v18.0.0

- 💔 `ReadTask.for()` now takes an options hash, which includes the new `defaultVideosToUTC` option.

- 🐞 Videos now default to UTC, unless there is a `TimeZone`, `OffsetTime`, `OffsetTimeOriginal`, `OffsetTimeDigitized`, or `TimeZoneOffset` tag value. Thanks for the [bug report](https://github.com/photostructure/exiftool-vendored.js/issues/113), @mrbrahman!

- 🌱 ExifTool upgraded to [v12.45](https://exiftool.org/history.html#v12.45).

### v17.1.0

- ✨ `ExifDateTime` and `ExifDate` now have a `toMillis()` to render in
  milliseconds from common epoch

- 📦 Expose `closeChildProcesses` from underlying BatchCluster instance

- 🐞 Pull in [batch-cluster bugfix](https://github.com/photostructure/batch-cluster.js/blob/main/CHANGELOG.md#v1042)

(Note that this build _does not_ pull in ExifTool v12.44, [due to this bug](https://exiftool.org/forum/index.php?topic=13863.0))

### v17.0.1

- 🐞 `reasonableTzOffsetMinutes()`, `extractOffset()`, and
  `offsetMinutesToZoneName()` handle `UnsetZone` properly. This shouldn't normally come into play, as this would require serialization of the unset timezone, but... why not, eh?

### v17.0.0

- 💔 Luxon has a [breaking change](https://moment.github.io/luxon/#/upgrading?id=_2x-to-30). Please verify that date parsing and zone assignments work as expected.

- 🌱 ExifTool upgraded to [v12.43](https://exiftool.org/history.html#v12.43).

- 🐞 `UnsetZone` now uses [`Info.normalizeZone()`](https://moment.github.io/luxon/api-docs/index.html#info).

- 📦 Updated dependencies

### v16.5.1

- 🌱 ExifTool upgraded to [v12.42](https://exiftool.org/history.html#v12.42).

- 📦 Updated dependencies

- 📦 Dropped Node v12 from GitHub Actions CI

- 📦 Added [RELEASE.md](https://github.com/photostructure/exiftool-vendored.js/blob/main/RELEASE.md)

### v16.4.0

- 🐞 Struct values are now properly encoded when writing. Specifically, prior
  versions didn't support JSON string values (and now WriteTask knows how to
  serialize those characters to make ExifTool happy)

- 📦/💔 `String.htmlEncode` was made private: it was a special-purpose function
  just for `WriteTask`.

- 📦 Added Node 18 to test matrix. Node 12 will be dropped from support in the
  next version.

- 📦 Updated dependencies

### v16.3.0

- ✨ Added `ExifDateTime.fromMillis()`

- 📦 Fixed hanging sentence in README. Rebuild docs.

- 📦 Migrated `omit()` to `Object`.

### v16.2.0

- ✨ Added read/write support for
  [History](https://exiftool.org/TagNames/XMP.html#ResourceEvent) and
  [Versions](https://exiftool.org/TagNames/XMP.html#Version) structs.

  - These two tags return typed optional struct arrays.

  - Via the new `StructAppendTags` interface, `ExifTool.write()` now accepts
    plus-suffixed variants of these tags to append to existing records.

- 🌱 ExifTool upgraded to [v12.41](https://exiftool.org/history.html#v12.41).

- 📦 Updated dependencies

### v16.1.0

- ✨ Updated dependencies, including batch-cluster
  [v10.4.0](https://github.com/photostructure/batch-cluster.js/blob/main/CHANGELOG.md#v1040)).

  This new version will detect when tasks are rejected (due to parsing issues or
  any other reason), and in that case, the child `exiftool` process will be
  verified to be "healthy" before being put back into the service pool.

### v16.0.0

- 💔/🐞 Timezone extraction has been adjusted: if there is a GPS location, we'll
  prefer that `tzlookup` as the authoritative timezone offset. If there isn't
  GPS lat/lon, we'll use `Timezone`, `OffsetTime`, or `TimeZoneOffset`. If those
  are missing, we'll infer the offset from UTC offsets.

  Prior builds would defer to the offset in `Timezone`, `OffsetTime`, or
  `TimeZoneOffset`, but GPS is more reliable, and results in a proper time zone
  (like `America/Los_Angeles`). Zone names work correctly even when times are
  adjusted across daylight savings offset boundaries.

- 💔/🐞 Timezone application is now has been improved: if a timezone can be
  extracted for a given file, `ExifTool.read()` will now make all `ExifDateTime`
  entries match that timezone. The timestamps should refer to the same
  timestamp/seconds-from-common-epoch, but "local time" may be different as
  we've adjusted the timezone accordingly.

  Metadata sometimes includes a timezone offset, and sometimes it doesn't, and
  it's all pretty inconsistent, but worse, prior versions would sometimes
  inherit the current system timezone for an arbitrary subset of tags. This
  version should remove the system timezone "leaking" into your metadata values.

  As an example, if you took a photo with GPS information from Rome (CET,
  UTC+1), and your computer is in California with `TZ=America/Los_Angeles`,
  prior versions could return `CreateDate: 2022-02-02 02:02:22-07:00`. This
  version will translate that time into `CreateDate: 2022-02-02 11:02:22+01:00`.

  Note that this fix results in `ExifTool.read()` rendering different `ExifDateTime`
  values from prior versions, so I bumped the major version to highlight this
  change.

- 💔 `Tags` is automatically generated by `mktags`, which now has a set of
  "required" tags with type and group metadata to ensure a core set of tags
  don't disappear or change types.

  As a reminder, the `Tags` interface is only a subset of fields returned, due
  to TypeScript limitations. `ExifTool.read()` still returns all values that ExifTool
  provides.

- 🐞 Fixed a bunch of broken API links in the README due to `typedoc` changing
  URLs. Harumph.
- 🐞 Prior versions of `ExifDateTime.parseISO` would accept just time or date
  strings.
- 🐞/📦 `TimeStamp` tags may now be properly parsed as `ExifDateTime`.
- 📦 Added performance section to the README.

- 📦 Timezone offset formatting changed slightly: the hour offset is no longer
  zero-padded, which better matches the Luxon implementation we use internally.

- 📦 `ExifDateTime` caches the result of `toDateTime` now, which may save a
  couple extra objects fed to the GC.

- 📦 Updated dependencies, including batch-cluster
  [v10.3.2](https://github.com/photostructure/batch-cluster.js/blob/main/CHANGELOG.md#v1032)),
  which fixed several race conditions and added several process performance
  improvements including support for zero-wait multi-process launches.

### v15.12.1

- 📦 Updated dependencies (batch-cluster
  [v10.3.0](https://github.com/photostructure/batch-cluster.js/blob/main/CHANGELOG.md#v1030)),
  including more pessimistic defaults for `streamFlushMillis` and new
  `noTaskData` event.

- 📦 Exported type signatures, `AdditionalWriteTags`, `ExpandedDateTags`,
  `Maybe`, `Omit`, and `Struct` to improve `typedoc`-generated documentation.
  Rebuilt docs.

### v15.12.0

- 📦 We now verify external `exiftool`s are healthy with a `-ver` ping every 30 seconds.

- 📦 Updated dependencies (batch-cluster [v10.2.0](https://github.com/photostructure/batch-cluster.js/blob/main/CHANGELOG.md#v1020)) that includes this [performance improvement/bugfix](https://github.com/photostructure/batch-cluster.js/issues/15)

### v15.11.0

- 🌱 ExifTool upgraded to [v12.40](https://exiftool.org/history.html#v12.40).

- 📦 Updated dependencies (batch-cluster [v10.0.0](https://github.com/photostructure/batch-cluster.js/blob/main/CHANGELOG.md#v1000))

- 📦 Rebuild `Tags.ts` and docs

### v15.10.1

- 📦 Updated dependencies (batch-cluster v8.1.0)

- 📦 Rebuild docs

### v15.10.0

- 🌱 ExifTool upgraded to [v12.39](https://exiftool.org/history.html#v12.39).

- 🐞/📦 Include `@types/luxon` in `dependencies` (thanks, [davidmz](https://github.com/photostructure/exiftool-vendored.js/pull/108)!)

### v15.9.2

- 📦 Rebuild tags and docs with updated test images. Note that some `GPS` tags types changed to `string`: see v15.8.0.

### v15.9.1

- 📦 Exposed `UnsetZoneOffsetMinutes` from `Timezones`

### v15.9.0

- 📦 Exposed `UnsetZone` and `UnsetZoneName` from `Timezones`

### v15.8.0

- 🐞 `GPSDateTime` in prior versions could be incorrectly parsed, resulting in an incorrectly inferred current-date and encoded-time.

- 🐞 GPS latitude and longitude parsing could result in the incorrect hemisphere, depending on the version of ExifTool.

- 📦 The prior default of making all `GPS*` tags numeric has been reduced to only `GPSLatitude` and `GPSLongitude`, which means tags like `GPSImgDirectionRef` will now be something like "Magnetic North" instead of the more cryptic "M", and `GPSAltitudeRef` will now be "Below Sea Level" instead of "1".

### v15.7.0

- 🌱 ExifTool upgraded to [v12.38](https://exiftool.org/history.html#v12.38).

- ✨ Add specific support for [deleting values associated to existing tags](https://github.com/photostructure/exiftool-vendored.js/issues/104)

- 🐞 No-op `.write()` calls to sidecars are now gracefully no-op'ed.

- 📦 Added tests with and without retries (to validate stdout/stderr bugfixes in v8.0 of `batch-cluster`)

- 📦 Replace `orElse` calls with `??`

- 📦 Updated dependencies

### v15.6.0

- ✨ Added [serialization support](https://github.com/photostructure/exiftool-vendored.js/issues/102)

- 🌱 ExifTool upgraded to [v12.34](https://exiftool.org/history.html#v12.34).

### v15.5.0

- 🌱 ExifTool upgraded to [v12.33](https://exiftool.org/history.html#v12.33).

- 📦 Updated dependencies

- 📦 Now ignoring `yarn.lock`

### v15.4.0

- 🌱 ExifTool upgraded to [v12.31](https://exiftool.org/history.html#v12.31).

- 📦 Updated dependencies (including new TypeScript, which required import [adjustments](https://github.com/microsoft/TypeScript/issues/46027#issuecomment-926019016).

### v15.3.0

- ✨ `ExifTool.read` and `ExifTool.write` [now accept generics](https://github.com/photostructure/exiftool-vendored.js/issues/103).

- 🌱 ExifTool upgraded to [v12.30](https://exiftool.org/history.html#v12.30).

- 📦 Updated dependencies (including new Luxon and TypeScript)

- 📦 Rebuilt docs

### v15.2.0

- 📦 Updated dependencies (including [batch-cluster
  v7.1.0](https://github.com/photostructure/batch-cluster.js/blob/main/CHANGELOG.md#v710),
  which fixes a 2s startup delay

### v15.1.0

- 📦 Rebuild `Tags.ts` from more recent exemplars and tag type overrides
  (v15.0.0 changed to `Keywords: string`, this version reverts that change)

### v15.0.0

- 💔 TypeScript now renders modern (ES2018) JavaScript, which requires a
  [supported version of Node.js](https://nodejs.org/en/about/releases/).

- ✨ New `ExifTool.extractBinaryTagToBuffer()`: [extract binary tags directly into a
  `Buffer`](https://github.com/photostructure/exiftool-vendored.js/issues/99)
  (watch out for memory bloat from very large binary tag payloads!)

- ✨ Expose `ExifTool.childEndCounts` (counts of why child processes were recycled: useful for debugging)

- 📦 Updated dependencies (including [batch-cluster v7.0.0](https://github.com/photostructure/batch-cluster.js/blob/main/CHANGELOG.md#v700))

### v14.6.2

- 📦 Updated batch-cluster (support for listing current tasks)

### v14.6.1

- 📦 Updated batch-cluster (support for nullable pids)

### v14.6.0

- 🌱 ExifTool upgraded to [v12.28](https://exiftool.org/history.html#v12.28).

- 📦 Updated dependencies

### v14.5.0

- 🌱 ExifTool upgraded to [v12.26](https://exiftool.org/history.html#v12.26).

- 📦 Updated dependencies

### v14.4.0

- ✨ Added `ExifDate.rawValue`

- 📦 Updated dependencies

### v14.3.0 🔥

- 🔥/🌱 ExifTool upgraded to [v12.25](https://exiftool.org/history.html#v12.25).

  **All users should upgrade to this version as soon as possible**, as this should
  address
  [CVE-2021-22204](https://twitter.com/wcbowling/status/1385803927321415687).

- 📦 Updated dependencies

### v14.2.0

- 🌱 ExifTool upgraded to [v12.23](https://exiftool.org/history.html#v12.23)

### v14.1.1

- 📦 Republish of 14.1.0 (`np` failed to publish 14.1.0 properly)

### v14.1.0

- 🌱 ExifTool upgraded to [v12.21](https://exiftool.org/history.html#v12.21)

- 📦 Stopped excluding sourcemaps

- 📦 Updated dependencies

### v14.0.0

- 💔 `ExifDateTime.zone` will now return the actual IANA zone name (like `America/Los_Angeles`) rather than the time offset. This addresses issues with timezones like `Europe/Kiev` where, from 1900-1924, had an offset of `UTC +2:02:04`.

- ✨ Added `ExifDateTime.isValid`

- 🌱 ExifTool upgraded to [v12.19](https://exiftool.org/history.html#v12.19)

- 📦 Rebuilt Tags.ts and docs

- 📦 Updated dependencies

### v13.2.0

- 🌱 ExifTool upgraded to [v12.18](https://exiftool.org/history.html#v12.18)

- 📦 Updated dependencies

### v13.1.0

- 🐞 More complex characters, like emoji that use compound codepoints, like 🦍,
  🦄, or 🚵‍♀️, are now supported. See
  [#87](https://github.com/photostructure/exiftool-vendored.js/issues/87) for
  more details. Thanks for the report, [Gabe
  Rodriguez](https://github.com/grod220)!

- 🌱 ExifTool upgraded to [v12.14](https://exiftool.org/history.html#v12.14)

- 📦 [he](https://github.com/mathiasbynens/he) is now a dependency, which was
  required by the emoji bugfix.

- 📦 Updated dependencies

### v13.0.0

- 💔 The `Tags.ts` types have changed. **Some newly-found types were added, many
  rarely-occurring types have been removed, and `Tag` sub-interfaces have
  changed**. Tag retention heuristics had to be updated, as TypeScript would
  crash with `error TS2590: Expression produces a union type that is too complex to represent`.

  `mktags` now has a "safe" set of tags that will be retained, and a set of tags
  that are expressly excluded.

  These changes won't prevent all type changes from happening in the future, but
  will prevent these more-common tags from being removed completely.

  As several tags are found in several different
  [groups](https://exiftool.org/TagNames/index.html), `mktags` now tries to
  place tags first in `FileTags` and `EXIFTags` groups before more proprietary
  APP groups, which should help future interface stability. (This explains why
  `MIMEType` moved to `FileTags`, for example).

- 🌱 ExifTool upgraded to [v12.12](https://exiftool.org/history.html#v12.12).

  Note that this version renders file sizes a bit differently: "756 kB" will now
  be rendered as "756 KiB".

### v12.3.1

- 📦 Removed dev dependency on `npm-check-updates`, as it no longer supports
  Node v10 (wth, ncu)

### v12.3.0

- 🌱 ExifTool upgraded to [v12.10](https://exiftool.org/history.html#v12.10)
- 📦 Rebuilt Tags.ts and docs
- 📦 Updated dependencies

### v12.2.0

- 🌱 ExifTool upgraded to [v12.06](https://exiftool.org/history.html#v12.06)
- 📦 Added quoted-file test

### v12.1.0

- 🌱 ExifTool upgraded to [v12.05](https://exiftool.org/history.html#v12.05)
- 📦 Updated dependencies

### v12.0.0

- 💔 `ExifDateTime.toISOString()` now returns `string | undefined` (as it
  proxies for Luxon's `DateTime.toISO()`, which now may return `null`.)
- 🌱 ExifTool upgraded to [v12.04](https://exiftool.org/history.html#v12.04)
- 📦 Rebuilt Tags.ts and docs
- 📦 Updated dependencies

### v11.5.0

- 🐞 `ExifDateTime` and `ExifDate` no longer accept just a year or year and month.
- 📦 Updated dependencies

### v11.4.0

- 🌱 ExifTool upgraded to [v12.01](https://exiftool.org/history.html#v12.01)
- ✨ ExifTool now takes a `Logger` thunk in the constructor options.
- 📦 Updated dependencies

### v11.3.0

- 🌱 ExifTool upgraded to [v11.98](https://exiftool.org/history.html#v11.98)
- 📦 BinaryExtractionTasks don't bother retrying when binary payloads are
  missing (which turns out to be a common issue)
- 📦 ExifToolTask is now exported
- 📦 Updated dependencies

### v11.2.0

- 🌱 ExifTool upgraded to [v11.95](https://exiftool.org/history.html#v11.95)
- 📦 Updated dependencies

### v11.1.0

- 📦 Updated dependencies, including `batch-cluster`. The new
  `maxIdleMsPerProcess` option shuts down ExifTool processes automatically if
  they are idle for longer than `maxIdleMsPerProcess` milliseconds. New
  processes are forked when needed.

### v11.0.0

- 💔 **Breaking change:** A number of tags were removed from `Tags` because we
  were getting dangerously close to TypeScript's `error TS2590: Expression produces a union type that is too complex to represent.`
- 🌱 ExifTool upgraded to [v11.93](https://exiftool.org/history.html#v11.93)

### v10.1.0

- 🐞 ExifTool doesn't (currently) respect `-ignoreMinorErrors` when extracting
  binary blobs. `BinaryExtractionTask` now assumes stderr messages matching
  `/^warning: /` are not actually errors.
- 🌱 ExifTool upgraded to [v11.92](https://exiftool.org/history.html#v11.92)
- 📦 Updated dependencies
- 📦 Prettier 2.0.0 pulled in and codebase reformatted with new defaults, causing huge (no-op) diff.

### v10.0.0

- 💔 **Breaking change:** For the past many major versions, when date and time
  fields are invalid, this library returns the raw (invalid) string provided by
  ExifTool, rather than an instance of `ExifDateTime`, `ExifDate`, or
  `ExifTime`. The `Tag` types now reflect this, but you'll _probably need to
  update your code_. See
  [#73](https://github.com/photostructure/exiftool-vendored.js/issues/73) for
  more context.
- 🌱 ExifTool upgraded to [v11.91](https://exiftool.org/history.html#v11.91)
- 📦 Updated dependencies

### v9.7.0

- 🐞/✨ Date, DateTime, and Time tags can now ISO formatted. See
  [#71](https://github.com/photostructure/exiftool-vendored.js/issues/71).
  Thanks for the report, [Roland Ayala](https://github.com/rolanday)!

### v9.6.0

- 🌱 ExifTool upgraded to [v1