fix(deps): update dependency exiftool-vendored to v29 #14220
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^28.3.1
->^29.0.0
Release Notes
photostructure/exiftool-vendored.js (exiftool-vendored)
v29.0.0
Compare Source
💔/🐞/📦 ExifTool sometimes returns
boolean
values for some tags, likeSemanticStylePreset
, but uses "Yes" or "No" values for other tags, likeGPSValid
(TIL!). If the tag name ends inValid
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
to10
. 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 yourstreamFlushMillis
.💔 TypeScript now emits ES2022, which requires Node.js 18.
GPS improvements
🐞/📦 GPS Latitude and GPS Longitude values are now parsed from DMS notation, 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
andGPSLongitude
to theExifToolOptions.numericTags
array.🐞/📦 If
ExifToolOptions.geolocation
is enabled, andGeolocationPosition
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*
andGeolocation*
metadata will be omitted fromExifTool.readTags()
. Prior versions let some values (likeGPSCoordinates
) 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 setGPSLatitudeRef
andGPSLongitudeRef
if lat/lon are provided but references are unspecified. More tests were added to verify this workaround. On reads,GPSLatitudeRef
andGPSLongitudeRef
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
andgeolocation
weretrue
, (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
Compare Source
Important: ExifTool versions use the format
NN.NN
and do not follow semantic versioning. The version from ExifTool will not parse correctly with thesemver
library (for the next 10 versions) since they are zero- padded.🌱 Upgraded ExifTool to version 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.
Configuration
📅 Schedule: Branch creation - "on tuesday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.