Skip to content

Releases: influxdata/datafusion-udf-wasm

WASM Binaries 2026-03-09T12:51:03+00:00

09 Mar 13:13

Choose a tag to compare

WASM guest binaries.

Build Metadata

Commit: f0a65b2773d4a0f1b64ed31dd96ef7be7ffd7942
Build Timestamp: 2026-03-09T12:51:03+00:00
Build Attestation: https://github.com/influxdata/datafusion-udf-wasm/attestations/20793493

WIT Interface

The WIT interface — used between host and guest — is: 0.4.0

If host & guest are out of sync, you will get an error that looks like this:

Context("link WASM components", External(Error { context: "initialize bindings", source: no exported instance named `datafusion-udf-wasm:udf/[email protected]`

Dependency Versions

These are the versions of the major dependencies:

Dependency Version
Arrow 57.2.0
DataFusion 52.1.0
Wasmtime 42.0.1

WASM Binaries

We build the following targets:

  • example_add_one: "add one" Rust example UDF
  • example_sub_str: "sub str" Rust example UDF
  • datafusion_udf_wasm_python: Guest for Python-based UDFs, bundles CPython.

Each of them is provided in debug and release builds. The artifacts have the file extension .wasm.

Machine-Code Binaries

In addition to the WASM binary blobs, we also provide pre-compiled guests for various targets to be used with wasmtime. The artifacts have the file extension .elf.

⚠️ Using pre-build binaries requires you to validate the source and trust the binary. Using a binary blindly can lead to remote code execution, memory and data corruption, and all kinds of bad things. You can use the provided build attestation. ⚠️

Checksums & Attestation

We provide sha256 checksums for all artifacts in sha256sum.txt. You can use that file -- either directly or indirectly via its own checksum -- to safely pin all artifacts of this release. We also provide build attestation.

WASM Binaries 2026-02-25T15:30:37+00:00

25 Feb 15:52
9f28571

Choose a tag to compare

WASM guest binaries.

Build Metadata

Commit: 9f285719af532cec123963e1cbce522d9e366c29
Build Timestamp: 2026-02-25T15:30:37+00:00
Build Attestation: https://github.com/influxdata/datafusion-udf-wasm/attestations/19778175

WIT Interface

The WIT interface — used between host and guest — is: 0.4.0

If host & guest are out of sync, you will get an error that looks like this:

Context("link WASM components", External(Error { context: "initialize bindings", source: no exported instance named `datafusion-udf-wasm:udf/[email protected]`

Dependency Versions

These are the versions of the major dependencies:

Dependency Version
Arrow 57.2.0
DataFusion 52.1.0
Wasmtime 42.0.0

WASM Binaries

We build the following targets:

  • example_add_one: "add one" Rust example UDF
  • example_sub_str: "sub str" Rust example UDF
  • datafusion_udf_wasm_python: Guest for Python-based UDFs, bundles CPython.

Each of them is provided in debug and release builds. The artifacts have the file extension .wasm.

Machine-Code Binaries

In addition to the WASM binary blobs, we also provide pre-compiled guests for various targets to be used with wasmtime. The artifacts have the file extension .elf.

⚠️ Using pre-build binaries requires you to validate the source and trust the binary. Using a binary blindly can lead to remote code execution, memory and data corruption, and all kinds of bad things. You can use the provided build attestation. ⚠️

Checksums & Attestation

We provide sha256 checksums for all artifacts in sha256sum.txt. You can use that file -- either directly or indirectly via its own checksum -- to safely pin all artifacts of this release. We also provide build attestation.

WASM Binaries 2026-02-06T12:21:55+00:00

06 Feb 12:40
8c49c2f

Choose a tag to compare

WASM guest binaries.

Build Metadata

Commit: 8c49c2f29158e6d3fbe11ca1e936b0a5948690bd
Build Timestamp: 2026-02-06T12:21:55+00:00
Build Attestation: https://github.com/influxdata/datafusion-udf-wasm/attestations/18338968

WIT Interface

The WIT interface — used between host and guest — is: 0.4.0

If host & guest are out of sync, you will get an error that looks like this:

Context("link WASM components", External(Error { context: "initialize bindings", source: no exported instance named `datafusion-udf-wasm:udf/[email protected]`

Dependency Versions

These are the versions of the major dependencies:

Dependency Version
Arrow 57.2.0
DataFusion 52.1.0
Wasmtime 41.0.3

WASM Binaries

We build the following targets:

  • example_add_one: "add one" Rust example UDF
  • datafusion_udf_wasm_python: Guest for Python-based UDFs, bundles CPython.

Each of them is provided in debug and release builds. The artifacts have the file extension .wasm.

Machine-Code Binaries

In addition to the WASM binary blobs, we also provide pre-compiled guests for various targets to be used with wasmtime. The artifacts have the file extension .elf.

⚠️ Using pre-build binaries requires you to validate the source and trust the binary. Using a binary blindly can lead to remote code execution, memory and data corruption, and all kinds of bad things. You can use the provided build attestation. ⚠️

Checksums & Attestation

We provide sha256 checksums for all artifacts in sha256sum.txt. You can use that file -- either directly or indirectly via its own checksum -- to safely pin all artifacts of this release. We also provide build attestation.

WASM Binaries 2026-01-28T11:46:19+00:00

28 Jan 12:06

Choose a tag to compare

WASM guest binaries.

Build Metadata

Commit: 89ab4ae6312c3a44859ddd43d9df4d4300d3086a
Build Timestamp: 2026-01-28T11:46:19+00:00
Build Attestation: https://github.com/influxdata/datafusion-udf-wasm/attestations/17599407

WIT Interface

The WIT interface — used between host and guest — is: 0.2.0

If host & guest are out of sync, you will get an error that looks like this:

Context("link WASM components", External(Error { context: "initialize bindings", source: no exported instance named `datafusion-udf-wasm:udf/[email protected]`

Dependency Versions

These are the versions of the major dependencies:

Dependency Version
Arrow 57.2.0
DataFusion 51.0.0
Wasmtime 41.0.1

WASM Binaries

We build the following targets:

  • example_add_one: "add one" Rust example UDF
  • datafusion_udf_wasm_python: Guest for Python-based UDFs, bundles CPython.

Each of them is provided in debug and release builds. The artifacts have the file extension .wasm.

Machine-Code Binaries

In addition to the WASM binary blobs, we also provide pre-compiled guests for various targets to be used with wasmtime. The artifacts have the file extension .elf.

⚠️ Using pre-build binaries requires you to validate the source and trust the binary. Using a binary blindly can lead to remote code execution, memory and data corruption, and all kinds of bad things. You can use the provided build attestation. ⚠️

Checksums & Attestation

We provide sha256 checksums for all artifacts in sha256sum.txt. You can use that file -- either directly or indirectly via its own checksum -- to safely pin all artifacts of this release. We also provide build attestation.

WASM Binaries 2026-01-21T01:05:14+00:00

21 Jan 01:25

Choose a tag to compare

WASM guest binaries.

Build Metadata

Commit: 9b2243ad3305ca3e29af38e8cc9097cb853f1fce
Wasmtime: 40.0.1
Build Timestamp: 2026-01-21T01:05:14+00:00
Build Attestation: https://github.com/influxdata/datafusion-udf-wasm/attestations/17040771

WASM Binaries

We build the following targets:

  • example_add_one: "add one" Rust example UDF
  • datafusion_udf_wasm_python: Guest for Python-based UDFs, bundles CPython.

Each of them is provided in debug and release builds. The artifacts have the file extension .wasm.

Machine-Code Binaries

In addition to the WASM binary blobs, we also provide pre-compiled guests for various targets to be used with wasmtime. The artifacts have the file extension .elf.

⚠️ Using pre-build binaries requires you to validate the source and trust the binary. Using a binary blindly can lead to remote code execution, memory and data corruption, and all kinds of bad things. You can use the provided build attestation. ⚠️

Checksums & Attestation

We provide sha256 checksums for all artifacts in sha256sum.txt. You can use that file -- either directly or indirectly via its own checksum -- to safely pin all artifacts of this release. We also provide build attestation.

WASM Binaries 2026-01-20T22:26:01+00:00

20 Jan 22:45
b66c76f

Choose a tag to compare

WASM guest binaries.

Build Metadata

Commit: b66c76fd7c54dc6caac079405000a5f54f65ca38
Wasmtime: 40.0.2
Build Timestamp: 2026-01-20T22:26:01+00:00
Build Attestation: https://github.com/influxdata/datafusion-udf-wasm/attestations/17034121

WASM Binaries

We build the following targets:

  • example_add_one: "add one" Rust example UDF
  • datafusion_udf_wasm_python: Guest for Python-based UDFs, bundles CPython.

Each of them is provided in debug and release builds. The artifacts have the file extension .wasm.

Machine-Code Binaries

In addition to the WASM binary blobs, we also provide pre-compiled guests for various targets to be used with wasmtime. The artifacts have the file extension .elf.

⚠️ Using pre-build binaries requires you to validate the source and trust the binary. Using a binary blindly can lead to remote code execution, memory and data corruption, and all kinds of bad things. You can use the provided build attestation. ⚠️

Checksums & Attestation

We provide sha256 checksums for all artifacts in sha256sum.txt. You can use that file -- either directly or indirectly via its own checksum -- to safely pin all artifacts of this release. We also provide build attestation.

WASM Binaries 2026-01-14T13:55:42+00:00

14 Jan 14:15
5157223

Choose a tag to compare

WASM guest binaries.

Build Metadata

Commit: 5157223f615e58458e62cd0fc1dba42a87bd1196
Wasmtime: 40.0.1
Build Timestamp: 2026-01-14T13:55:42+00:00
Build Attestation: https://github.com/influxdata/datafusion-udf-wasm/attestations/16619507

WASM Binaries

We build the following targets:

  • example_add_one: "add one" Rust example UDF
  • datafusion_udf_wasm_python: Guest for Python-based UDFs, bundles CPython.

Each of them is provided in debug and release builds. The artifacts have the file extension .wasm.

Machine-Code Binaries

In addition to the WASM binary blobs, we also provide pre-compiled guests for various targets to be used with wasmtime. The artifacts have the file extension .elf.

⚠️ Using pre-build binaries requires you to validate the source and trust the binary. Using a binary blindly can lead to remote code execution, memory and data corruption, and all kinds of bad things. You can use the provided build attestation. ⚠️

Checksums & Attestation

We provide sha256 checksums for all artifacts in sha256sum.txt. You can use that file -- either directly or indirectly via its own checksum -- to safely pin all artifacts of this release. We also provide build attestation.

WASM Binaries 2026-01-05T14:07:35+00:00

05 Jan 14:27
3a1a690

Choose a tag to compare

WASM guest binaries.

Build Metadata

Commit: 3a1a690a872b44c5aba994c196ef4e039224c6dd
Wasmtime: 40.0.0
Build Timestamp: 2026-01-05T14:07:35+00:00
Build Attestation: https://github.com/influxdata/datafusion-udf-wasm/attestations/16019056

WASM Binaries

We build the following targets:

  • example_add_one: "add one" Rust example UDF
  • datafusion_udf_wasm_python: Guest for Python-based UDFs, bundles CPython.

Each of them is provided in debug and release builds. The artifacts have the file extension .wasm.

Machine-Code Binaries

In addition to the WASM binary blobs, we also provide pre-compiled guests for various targets to be used with wasmtime. The artifacts have the file extension .elf.

⚠️ Using pre-build binaries requires you to validate the source and trust the binary. Using a binary blindly can lead to remote code execution, memory and data corruption, and all kinds of bad things. You can use the provided build attestation. ⚠️

Checksums & Attestation

We provide sha256 checksums for all artifacts in sha256sum.txt. You can use that file -- either directly or indirectly via its own checksum -- to safely pin all artifacts of this release. We also provide build attestation.

WASM Binaries 2025-12-11T16:45:01+00:00

11 Dec 17:04

Choose a tag to compare

WASM guest binaries.

Build Metadata

Commit: 27d20de11f0c07544133d4d79af7398ccd256343
Wasmtime: 39.0.1
Build Timestamp: 2025-12-11T16:45:01+00:00
Build Attestation: https://github.com/influxdata/datafusion-udf-wasm/attestations/14940639

WASM Binaries

We build the following targets:

  • example_add_one: "add one" Rust example UDF
  • datafusion_udf_wasm_python: Guest for Python-based UDFs, bundles CPython.

Each of them is provided in debug and release builds. The artifacts have the file extension .wasm.

Machine-Code Binaries

In addition to the WASM binary blobs, we also provide pre-compiled guests for various targets to be used with wasmtime. The artifacts have the file extension .elf.

⚠️ Using pre-build binaries requires you to validate the source and trust the binary. Using a binary blindly can lead to remote code execution, memory and data corruption, and all kinds of bad things. You can use the provided build attestation. ⚠️

Checksums & Attestation

We provide sha256 checksums for all artifacts in sha256sum.txt. You can use that file -- either directly or indirectly via its own checksum -- to safely pin all artifacts of this release. We also provide build attestation.

WASM Binaries 2025-12-09T16:51:51+00:00

09 Dec 17:10

Choose a tag to compare

WASM guest binaries.

Build Metadata

Commit: 76c0d72017b0908c59a8af5ad786797c874de34f
Wasmtime: 39.0.1
Build Timestamp: 2025-12-09T16:51:51+00:00
Build Attestation: https://github.com/influxdata/datafusion-udf-wasm/attestations/14786987

WASM Binaries

We build the following targets:

  • example_add_one: "add one" Rust example UDF
  • datafusion_udf_wasm_python: Guest for Python-based UDFs, bundles CPython.

Each of them is provided debug and release build. The artifacts have the file extension .wasm.

Machine-Code Binaries

In addition to the WASM binary blobs, we also provide pre-compiled guests for various targets to be used with wasmtime. The artifacts have the file extension .so.

⚠️ Using pre-build binaries requires you to validate the source and trust the binary. Using a binary blindly can lead to remote code execution, memory and data corruption, and all kinds of bad things. You can use the provided build attestation. ⚠️

Checksums & Attestation

We provide sha256 checksums for all artifacts in sha256sum.txt. You can use that file -- either directly or indirectly via its own checksum -- to safely pin all artifacts of this release. We also provide [build attestation]({{ steps.attestation.outputs.attestation-url }}).