Skip to content

Support Policy

This page states which heliaRT releases Ambiq supports, how long critical fixes stay available, and how much notice you get before something is removed.

Supported Releases

Ambiq supports the current and previous minor releases.

Practically, that means the newest minor version and the one before it receive bug fixes and are the versions Ambiq expects to reproduce reports against.

Track Version Status
Current minor v1.20.x Supported
Previous minor v1.19.x Supported
Older minors v1.17.x and earlier Not supported

v1.18.0 is withdrawn and does not count as a supported minor: its heliaCORE pin is defective for the float32 and float16 kernels (NaN handling and the FP16 LSTM), and v1.19.0 supersedes it. Users on v1.18.0 should upgrade to the current minor. The helia-rt-v1.18.0 tag remains in place for reproducibility.

Being supported means running the latest patch release of a supported minor. A defect that is already fixed in a later patch of your minor is addressed by upgrading to that patch.

Release tag naming

Releases from v1.16.0 onward are tagged helia-rt-v<version>. v1.5.0–v1.15.0 use heliaRT-v<version> — v1.7.0 carries both HeliaRT-v1.7.0, which holds the release, and heliaRT-v1.7.0. v1.0.0–v1.3.0 predate the prefix and are tagged v<version>. All three schemes appear on the Releases page; legacy tags were not renamed.

Critical And Security Fixes

Ambiq provides critical/security fixes for 12 months. The 12 months run from the release date of the minor, not from the date it was superseded.

A fix is critical if it addresses either of:

  • a security vulnerability, or
  • a wrong-inference or data-corruption defect with no workaround.

This window applies within the current and previous minors only. Minors older than that are not eligible for critical fixes, whatever their release date.

Reporting A Security Issue

Report anything you believe is a security issue to support.aitg@ambiq.com rather than opening a public issue. GitHub private vulnerability reporting is planned — see #219 — but is not yet the intake channel.

Deprecation Notice

When a supported capability is scheduled for removal, Ambiq gives at least 90 days deprecation notice.

Notices are published in three places, so no single channel has to be watched:

  • the release notes for the release that announces the deprecation,
  • CHANGELOG.md, and
  • a banner on this documentation site.

The surfaces covered by this commitment are the public API, build options, and supported toolchains and targets.

Known Unsupported Behavior

Stateful/streaming quantized HELIA LSTM: the state-persistence fix is released. The change landed on main in #197 after v1.17.0 was cut and first shipped in v1.18.0, where it is listed in the release notes. It is carried forward in v1.19.0. Because v1.18.0 is withdrawn (see Supported Releases), take this fix from v1.19.0.

Releases up to and including v1.17.0 do not contain it. On those releases, treat quantized UNIDIRECTIONAL_SEQUENCE_LSTM as single-shot.

This statement is quantized-only. It says nothing about the FP16 and FP32 LSTM paths — see FP16 and FP32 for those.

Where heliaRT May Run

Support scope and license scope are different things. Development, testing, validation, benchmarking, CI, emulation, and simulation are permitted on non-Ambiq CPUs; production or commercial deployment is licensed for Ambiq-manufactured CPUs only. See Attribution and Trademarks for the license boundary, and the repository LICENSE for the governing terms.

Getting Help

Next Steps