Skip to content

v0.12.2

Choose a tag to compare

@github-actions github-actions released this 15 Oct 00:10
· 459 commits to main since this release
2410c78
  • Pair this release with Apple companions llamadart_llama_cpp_flutter
    0.0.23, llamadart_litert_lm_flutter 0.0.16 and
    llamadart_stable_diffusion_flutter 0.0.3, which link native runtimes
    v0.6.0-3, v0.18.0-1 and v0.2.0-3, respectively.

  • The default llama.cpp runtime is now leehack/llamadart-native@v0.6.0-3,
    whose Apple frameworks declare their minimum OS version (iOS 16.4, macOS
    13.3) (#1037).

  • Flutter iOS and macOS apps that keep llamadart_llama_cpp_flutter 0.0.22
    (native v0.6.0-2, the same binaries) still build, with a warning to depend
    on ^0.0.23 for the frameworks' minimum OS version metadata. Any other
    mismatched companion still fails the build, and the error names the
    companion version to depend on
    (#1063).

  • The default LiteRT-LM runtime is now leehack/litert-lm-native@v0.18.0-1,
    whose macOS runtimes are arm64 only. Universal Flutter macOS apps with
    llamadart_litert_lm_flutter now launch on Intel Macs and under Rosetta
    instead of aborting; LiteRT-LM throws LlamaUnsupportedException on x86_64
    macOS (litert-lm-native#72).

  • The build hook verifies every llama.cpp archive it downloads or reuses from
    its cache against a pinned SHA-256, or the release's SHA256SUMS when
    llamadart_native_tag or llamadart_native_repository overrides the
    release. A mismatched cached archive is downloaded again; a fresh download
    that does not match fails the build with NativeArchiveDigestException
    (#1015).

  • A .litertlm bundle in a directory the process cannot write, such as an
    iOS app bundle, no longer fails GPU engine creation on iOS and Linux when
    liteRtLmCacheDir is unset: the GPU engine reuses caches already there or
    runs without them (#976).

  • Image generation on Metal: ImageModelParams.vaeDirectConvolution: true
    throws LlamaUnsupportedException at load on iOS instead of returning
    corrupt images (#1044),
    and after a failed command buffer generation says the model must be
    reloaded and fails later generations on that engine with the same message
    (#1045).

  • A model cache directory that cannot be created, such as an unwritable
    ModelLoadOptions.cacheDirectory, throws LlamaModelException naming the
    directory instead of a raw FileSystemException
    (#894). A download that
    fails TLS certificate verification says so in its LlamaModelException,
    and TLS certificate and handshake failures are no longer retried
    (#978).

  • A ModelResolver that maps a remote source to a local mirror file now
    loads it when the download options set cacheDirectory, credentials or
    other download-only options, instead of throwing
    LlamaUnsupportedException
    (#897).

  • ModelParams.loras with more than one adapter or a scale other than 1.0
    throws LlamaUnsupportedException before any adapter downloads when the
    model loads in LiteRT-LM, by backend, format or .litertlm extension
    (#891).

  • The chat example no longer sends its stored Min-P to text to speech when
    the loaded runtime does not support Min-P
    (#747).

  • Aligned the default WebGPU bridge assets to v0.1.59, unchanged from 0.12.1:
    they embed llama.cpp v0.6.0, are qualified against native v0.6.0, and
    keep Web/native llama.cpp v0.6.0@d81235049384534c167caea52b85a694f6103d14
    parity; Web LiteRT-LM is @litert-lm/core@0.18.0. Immutable Web asset
    manifest:
    f823b10417b212ff1f66aa1c46bf78af7d9c393497dfcf0fa3a4f77adeb260eb.