Releases: zoellner/sharp-heic-lambda-layer
v6.1.0
What's Changed
- Update sharp to 0.35.1, libvips to 8.18.3, libheif to 1.23.0, libde265 to 1.0.18, libaom to 3.14.1 by @faradaytrs in #43
- Build flow updated for sharp 0.35 (explicit build step against global libvips, no more prebuilt binaries in the layer)
- Reduced build parallelism to avoid OOM on CodeBuild medium instances by @faradaytrs
- Build hardening: SHA256 verification for all source tarballs, pinned node-gyp/node-addon-api
- CodeBuild image updated to
aws/codebuild/amazonlinux-x86_64-standard:6.0
Full Changelog: v6.0.0...v6.1.0
Contributors
Assets 2
v6.0.0
What's Changed
- Update sharp to 0.34.5, libvips to 8.17.3, libheif to 1.21.2 by @faradaytrs
- Node.js 24 runtime support (nodejs24.x)
Full Changelog: v5.1.0...v6.0.0
Contributors
Assets 2
v5.1.0
Contributors
Assets 2
v5.0.0
What's Changed
- Node 22 + Sharp 0.34.1 + upstream changes by @faradaytrs in #37
Full Changelog: v4.2.0...v5.0.0
Contributors
Assets 2
v4.2.0
What's Changed
- Update sharp to 0.33.4, include av1 support for encoding and decoding by @faradaytrs in #33
New Contributors
- @faradaytrs made their first contribution in #33
Full Changelog: v4.1.3...v4.2.0
Contributors
Assets 2
v4.1.3
Major Release for node.js v20
Latest dependencies (including sharp@0.33.3) and updated build process
For those using CodeBuild: make sure to use an image that supports node.js v20 (e.g. aws/codebuild/amazonlinux2-x86_64-standard:5.0). See https://docs.aws.amazon.com/codebuild/latest/userguide/available-runtimes.html for details
Note that Releases/Tags v4.x before 4.1.3 don't work
v3.2.0
This will probably be the last release for node.js v16. It has slightly updated dependencies (see Readme for exact versions).
These are not the latest depdendencies available since the newer versions use completely different build processes and it just doesn't work well and I don't have the time to debug and tweak it all.
If someone wants to spend the time and create a PR I'm happy to test it.
Ultimately the focus should be on creating a working node.js v18 version