Bump exifreader from 4.41.0 to 4.45.0 in /e2e/nextjs-app

[dependabot]

Bumps exifreader from 4.41.0 to 4.45.0.

Release notes

Sourced from exifreader's releases.

4.45.0: Security fixes and custom build corrections

Changed

• A custom build that includes neither the exif nor the xmp module is now smaller. It no longer carries the code that computes the composite tags (FocalLength35efl, ScaleFactorTo35mmEquivalent and FieldOfView), which are derived from tags in those two groups and so could never be produced in such a build. A build with only PNG support ({"include": {"png": true}}) goes from 36002 to 34694 bytes, around 0.5 KiB gzipped. A custom build that includes either module produces a byte-identical bundle and returns the same tags.
• A custom build that excludes the exif module no longer carries the 0th, Exif, GPS and interoperability tag name tables. They came in whenever anything imported the shared tag name module, so a build that kept mpf carried them even though it could never read an Exif tag. Leaving them out takes a build configured with {"exclude": {"exif": true}} from 117324 down to 96920 bytes, around 5 KiB gzipped, and one configured with {"include": {"jpeg": true, "mpf": true}} from 54329 down to 32383 bytes, around 6 KiB gzipped. A custom build that includes exif produces a byte-identical bundle and returns the same tags.

Fixed

• A custom build whose include pattern names the thumbnail module but not exif now gets the exif module too, so it returns the Thumbnail tag. The build already meant to do this, but the condition could never be true, so such a build read no Exif data at all, with no warning and no error.
• The custom build module table no longer claims that mpf needs exif. MPF tags are read from their own JPEG segment, so an include pattern naming mpf without exif has always worked, and such a build stays smaller without the exif module.
• A custom build that excludes the exif module now keeps the mpf module instead of dropping it. Such a build gets bigger, since the MPF parser brings back the shared IFD reading code. It also copies out the sub-images that phone JPEGs embed, which costs time and memory, and with length: 'auto' it reads more of the file. A build that wants none of that can exclude mpf, and a build that already excludes mpf was never affected.
• The custom build module table now says that the photoshop module needs exif. Photoshop tags are read from Exif tags, so an include pattern naming photoshop without exif returns nothing.
• A custom build that includes the thumbnail module but neither jpeg nor webp, for example one paired with heic or avif, now returns the Thumbnail tag. The thumbnail was found in the Exif data and parsed and then dropped, so it was missing with no warning and no error. A build that also includes jpeg or webp was never affected.
• A custom build that includes the iptc, xmp, or icc module together with exif but without tiff now returns those tags when they are stored inside an Exif tag. Any format can carry them that way, not only TIFF, but they were only parsed when the tiff module was included, so such a build was missing them with no warning and no error. For IPTC in a HEIC, AVIF, WebP, or JPEG XL

... (truncated)

Changelog

Sourced from exifreader's changelog.

[4.45.0] - 2026-09-10

Changed

• A custom build that includes neither the exif nor the xmp module is now smaller. It no longer carries the code that computes the composite tags (FocalLength35efl, ScaleFactorTo35mmEquivalent and FieldOfView), which are derived from tags in those two groups and so could never be produced in such a build. A build with only PNG support ({"include": {"png": true}}) goes from 36002 to 34694 bytes, around 0.5 KiB gzipped. A custom build that includes either module produces a byte-identical bundle and returns the same tags.
• A custom build that excludes the exif module no longer carries the 0th, Exif, GPS and interoperability tag name tables. They came in whenever anything imported the shared tag name module, so a build that kept mpf carried them even though it could never read an Exif tag. Leaving them out takes a build configured with {"exclude": {"exif": true}} from 117324 down to 96920 bytes, around 5 KiB gzipped, and one configured with {"include": {"jpeg": true, "mpf": true}} from 54329 down to 32383 bytes, around 6 KiB gzipped. A custom build that includes exif produces a byte-identical bundle and returns the same tags.

Fixed

• A custom build whose include pattern names the thumbnail module but not exif now gets the exif module too, so it returns the Thumbnail tag. The build already meant to do this, but the condition could never be true, so such a build read no Exif data at all, with no warning and no error.
• The custom build module table no longer claims that mpf needs exif. MPF tags are read from their own JPEG segment, so an include pattern naming mpf without exif has always worked, and such a build stays smaller without the exif module.
• A custom build that excludes the exif module now keeps the mpf module instead of dropping it. Such a build gets bigger, since the MPF parser brings back the shared IFD reading code. It also copies out the sub-images that phone JPEGs embed, which costs time and memory, and with length: 'auto' it reads more of the file. A build that wants none of that can exclude mpf, and a build that already excludes mpf was never affected.
• The custom build module table now says that the photoshop module needs exif. Photoshop tags are read from Exif tags, so an include pattern naming photoshop without exif returns nothing.
• A custom build that includes the thumbnail module but neither jpeg nor webp, for example one paired with heic or avif, now returns the Thumbnail tag. The thumbnail was found in the Exif data and parsed and then dropped, so it was missing with no warning and no error. A build that also includes jpeg or webp was never affected.
• A custom build that includes the iptc, xmp, or icc module together with exif but without tiff now returns those tags when they are stored inside an Exif tag. Any format can carry them that way, not only TIFF, but they were only parsed when the tiff module was included, so such a build was missing

... (truncated)

Commits

• 5197961 4.45.0
• de48d27 Update changelog for 4.45.0
• f200a53 Copy a windowed DataView before parsing it
• 9a15744 Leave out the Exif tag name tables in custom builds without exif
• 57c0643 Leave out the PNG thumbnail IFD that carries no thumbnail image
• 9eeb47a Bound the number of ICC chunk descriptors kept while scanning a JPEG
• d3e47f6 Make the photoshop module follow exif in custom builds
• 00c6ef5 Leave out an Exif thumbnail whose declared range is outside the data
• 86eb872 Make the maker notes module follow exif in custom builds
• 90b1705 Keep the mpf module in custom builds that exclude exif
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.