Releases: akash-akya/vix
v0.23.0
What's Changed
- Fix incorrect image tensor shape in #129. This is a breaking change if you were relying on tensor shape field
Full Changelog: v0.22.0...v0.23.0
v0.22.0
What's Changed
- Precompile binaries for NIF version 2.17 to support OTP 26 by @akash-akya in #118
Full Changelog: v0.21.0...v0.22.0
v0.21.0
v0.20.0
What's Changed
- Make sure :ssl is available by @leandrocp in #115
New Contributors
- @leandrocp made their first contribution in #115
Full Changelog: v0.19.0...v0.20.0
v0.19.0
What's Changed
- Bump pre-built libvips version to current latest (
8.14.2
) in #110 - Support writing higher bitdepth heif/avif image in akash-akya/sharp-libvips@ac05f0d. Fixes #109
Full Changelog: v0.18.0...v0.19.0
v0.18.0
What's Changed
- Add power operator and
new_image_from_list
by @akash-akya in #105 - Fix typespec on generated functions for fetching image header fields by @haste in #106
- Correct image header typespec by @akash-akya in #108
New Contributors
Full Changelog: v0.17.0...v0.18.0
v0.17.0
Breaking Changes
1. Change additional output type from keyword list to map.
Few operations such as min
returns operation related metadata as last value of the returned tuple.
Previously, this value was a keyword list, now it is changed to a map to make it easy to access a single value from the metadata more intuitively when metadata contains multiple values.
If your code relies on value being a list then your code will break. You have to change to use map instead.
# previously
{:ok, out, [distance: distance]} = Vix.Vips.Operation.fill_nearest(image)
# should be changed to
{:ok, out, %{distance: distance}} = Vix.Vips.Operation.fill_nearest(image)
If you are accessing values using access
protocol, like opt[:field]
then no change is needed.
{:ok, min, opt} = Vix.Vips.Operation.min(image)
# no change needed
x = opt[:y]
2. Skip returning additional output values (flags) when it is empty
Previously in certain cases few operations used to return empty metadata as last value of tuple for example Operation.profile!
used to return {Image.t(), Image.t(), []}
, even when we know that the operation does not have any additional output values. With this release we don't, Operation.profile!
now returns {Image.t(), Image.t()}
. Please change your code accordingly and test.
Non-Breaking Changes
- Add math operators
- Inline operation documentation
- Correct typespec for function to fetch image header fields
- Add dialyzer and update CI to use cache
Full Changelog: v0.16.4...v0.17.0
v0.16.4
What's Changed
- Update castore dependency to 1.x by @premist in #97
- Cache musl compilers by @akash-akya in #99
New Contributors
Full Changelog: v0.16.3...v0.16.4
v0.16.3
What's Changed
- Create pre-built binaries for armv7l by @akash-akya in #96
Full Changelog: v0.16.2...v0.16.3
v0.16.3-alpha
Release to test prebuilt package for armv7l