Build on Rust 1.98 by tamnd · Pull Request #36 · tamnd/zu-python

tamnd · 2026-08-21T12:05:35Z

Closes#35.

tamnd/zu is on 1.98.0 as of tamnd/zu#516, and toolchains.toml there
is the one table that says which version every repository holds, so
this repository follows it. Four places name a version:

rust-toolchain.toml, which is what a local build reads
rust-version in Cargo.toml, the floor
the maturin steps in wheels.yml and install.yml, which name the
version themselves because the manylinux and musllinux containers do
not read the toolchain file

No source change was needed. chunks_exact_to_as_chunks, the new 1.98
lint that broke tamnd/zu and tamnd/zu-node, has nothing to fire on
here.

Checked locally on 1.98.0:

cargo check --all-targets, cargo fmt --all --check, and
cargo clippy --all-targets -- -D warnings clean
both feature rows CI builds:
--no-default-features --features pyo3/extension-module and
--features abi3t,pyo3/extension-module
pytest: 780 passed, 5 skipped

tamnd/zu moved to 1.98.0 and toolchains.toml is what says which version every repository holds, so this follows it: the toolchain file, the manifest floor, and the two maturin jobs that name the version themselves because the build container does not read the toolchain file. Nothing in the source needed changing. The 1.98 lint that caught the other repositories, chunks_exact_to_as_chunks, has nothing to fire on here. cargo check, fmt and clippy with -D warnings are clean on 1.98 for the default features and for both of the feature rows CI builds, and pytest is 780 passed, 5 skipped.

tamnd · 2026-08-21T12:05:35Z

Closes#35.

tamnd/zu is on 1.98.0 as of tamnd/zu#516, and toolchains.toml there
is the one table that says which version every repository holds, so
this repository follows it. Four places name a version:

rust-toolchain.toml, which is what a local build reads
rust-version in Cargo.toml, the floor
the maturin steps in wheels.yml and install.yml, which name the
version themselves because the manylinux and musllinux containers do
not read the toolchain file

No source change was needed. chunks_exact_to_as_chunks, the new 1.98
lint that broke tamnd/zu and tamnd/zu-node, has nothing to fire on
here.

Checked locally on 1.98.0:

cargo check --all-targets, cargo fmt --all --check, and
cargo clippy --all-targets -- -D warnings clean
both feature rows CI builds:
--no-default-features --features pyo3/extension-module and
--features abi3t,pyo3/extension-module
pytest: 780 passed, 5 skipped

tamnd/zu moved to 1.98.0 and toolchains.toml is what says which version every repository holds, so this follows it: the toolchain file, the manifest floor, and the two maturin jobs that name the version themselves because the build container does not read the toolchain file. Nothing in the source needed changing. The 1.98 lint that caught the other repositories, chunks_exact_to_as_chunks, has nothing to fire on here. cargo check, fmt and clippy with -D warnings are clean on 1.98 for the default features and for both of the feature rows CI builds, and pytest is 780 passed, 5 skipped.

tamnd · 2026-08-21T12:05:35Z

Closes#35.

tamnd/zu is on 1.98.0 as of tamnd/zu#516, and toolchains.toml there
is the one table that says which version every repository holds, so
this repository follows it. Four places name a version:

rust-toolchain.toml, which is what a local build reads
rust-version in Cargo.toml, the floor
the maturin steps in wheels.yml and install.yml, which name the
version themselves because the manylinux and musllinux containers do
not read the toolchain file

No source change was needed. chunks_exact_to_as_chunks, the new 1.98
lint that broke tamnd/zu and tamnd/zu-node, has nothing to fire on
here.

Checked locally on 1.98.0:

cargo check --all-targets, cargo fmt --all --check, and
cargo clippy --all-targets -- -D warnings clean
both feature rows CI builds:
--no-default-features --features pyo3/extension-module and
--features abi3t,pyo3/extension-module
pytest: 780 passed, 5 skipped

tamnd/zu moved to 1.98.0 and toolchains.toml is what says which version every repository holds, so this follows it: the toolchain file, the manifest floor, and the two maturin jobs that name the version themselves because the build container does not read the toolchain file. Nothing in the source needed changing. The 1.98 lint that caught the other repositories, chunks_exact_to_as_chunks, has nothing to fire on here. cargo check, fmt and clippy with -D warnings are clean on 1.98 for the default features and for both of the feature rows CI builds, and pytest is 780 passed, 5 skipped.

tamnd · 2026-08-21T12:05:35Z

Closes#35.

tamnd/zu is on 1.98.0 as of tamnd/zu#516, and toolchains.toml there
is the one table that says which version every repository holds, so
this repository follows it. Four places name a version:

rust-toolchain.toml, which is what a local build reads
rust-version in Cargo.toml, the floor
the maturin steps in wheels.yml and install.yml, which name the
version themselves because the manylinux and musllinux containers do
not read the toolchain file

No source change was needed. chunks_exact_to_as_chunks, the new 1.98
lint that broke tamnd/zu and tamnd/zu-node, has nothing to fire on
here.

Checked locally on 1.98.0:

cargo check --all-targets, cargo fmt --all --check, and
cargo clippy --all-targets -- -D warnings clean
both feature rows CI builds:
--no-default-features --features pyo3/extension-module and
--features abi3t,pyo3/extension-module
pytest: 780 passed, 5 skipped

tamnd/zu moved to 1.98.0 and toolchains.toml is what says which version every repository holds, so this follows it: the toolchain file, the manifest floor, and the two maturin jobs that name the version themselves because the build container does not read the toolchain file. Nothing in the source needed changing. The 1.98 lint that caught the other repositories, chunks_exact_to_as_chunks, has nothing to fire on here. cargo check, fmt and clippy with -D warnings are clean on 1.98 for the default features and for both of the feature rows CI builds, and pytest is 780 passed, 5 skipped.

tamnd · 2026-08-21T12:05:35Z

Closes#35.

tamnd/zu is on 1.98.0 as of tamnd/zu#516, and toolchains.toml there
is the one table that says which version every repository holds, so
this repository follows it. Four places name a version:

rust-toolchain.toml, which is what a local build reads
rust-version in Cargo.toml, the floor
the maturin steps in wheels.yml and install.yml, which name the
version themselves because the manylinux and musllinux containers do
not read the toolchain file

No source change was needed. chunks_exact_to_as_chunks, the new 1.98
lint that broke tamnd/zu and tamnd/zu-node, has nothing to fire on
here.

Checked locally on 1.98.0:

cargo check --all-targets, cargo fmt --all --check, and
cargo clippy --all-targets -- -D warnings clean
both feature rows CI builds:
--no-default-features --features pyo3/extension-module and
--features abi3t,pyo3/extension-module
pytest: 780 passed, 5 skipped

tamnd/zu moved to 1.98.0 and toolchains.toml is what says which version every repository holds, so this follows it: the toolchain file, the manifest floor, and the two maturin jobs that name the version themselves because the build container does not read the toolchain file. Nothing in the source needed changing. The 1.98 lint that caught the other repositories, chunks_exact_to_as_chunks, has nothing to fire on here. cargo check, fmt and clippy with -D warnings are clean on 1.98 for the default features and for both of the feature rows CI builds, and pytest is 780 passed, 5 skipped.

tamnd · 2026-08-21T12:05:35Z

Closes#35.

tamnd/zu is on 1.98.0 as of tamnd/zu#516, and toolchains.toml there
is the one table that says which version every repository holds, so
this repository follows it. Four places name a version:

rust-toolchain.toml, which is what a local build reads
rust-version in Cargo.toml, the floor
the maturin steps in wheels.yml and install.yml, which name the
version themselves because the manylinux and musllinux containers do
not read the toolchain file

No source change was needed. chunks_exact_to_as_chunks, the new 1.98
lint that broke tamnd/zu and tamnd/zu-node, has nothing to fire on
here.

Checked locally on 1.98.0:

cargo check --all-targets, cargo fmt --all --check, and
cargo clippy --all-targets -- -D warnings clean
both feature rows CI builds:
--no-default-features --features pyo3/extension-module and
--features abi3t,pyo3/extension-module
pytest: 780 passed, 5 skipped

tamnd/zu moved to 1.98.0 and toolchains.toml is what says which version every repository holds, so this follows it: the toolchain file, the manifest floor, and the two maturin jobs that name the version themselves because the build container does not read the toolchain file. Nothing in the source needed changing. The 1.98 lint that caught the other repositories, chunks_exact_to_as_chunks, has nothing to fire on here. cargo check, fmt and clippy with -D warnings are clean on 1.98 for the default features and for both of the feature rows CI builds, and pytest is 780 passed, 5 skipped.

tamnd · 2026-08-21T12:05:35Z

Closes#35.

tamnd/zu is on 1.98.0 as of tamnd/zu#516, and toolchains.toml there
is the one table that says which version every repository holds, so
this repository follows it. Four places name a version:

rust-toolchain.toml, which is what a local build reads
rust-version in Cargo.toml, the floor
the maturin steps in wheels.yml and install.yml, which name the
version themselves because the manylinux and musllinux containers do
not read the toolchain file

No source change was needed. chunks_exact_to_as_chunks, the new 1.98
lint that broke tamnd/zu and tamnd/zu-node, has nothing to fire on
here.

Checked locally on 1.98.0:

cargo check --all-targets, cargo fmt --all --check, and
cargo clippy --all-targets -- -D warnings clean
both feature rows CI builds:
--no-default-features --features pyo3/extension-module and
--features abi3t,pyo3/extension-module
pytest: 780 passed, 5 skipped

tamnd/zu moved to 1.98.0 and toolchains.toml is what says which version every repository holds, so this follows it: the toolchain file, the manifest floor, and the two maturin jobs that name the version themselves because the build container does not read the toolchain file. Nothing in the source needed changing. The 1.98 lint that caught the other repositories, chunks_exact_to_as_chunks, has nothing to fire on here. cargo check, fmt and clippy with -D warnings are clean on 1.98 for the default features and for both of the feature rows CI builds, and pytest is 780 passed, 5 skipped.

tamnd · 2026-08-21T12:05:35Z

Closes#35.

tamnd/zu is on 1.98.0 as of tamnd/zu#516, and toolchains.toml there
is the one table that says which version every repository holds, so
this repository follows it. Four places name a version:

rust-toolchain.toml, which is what a local build reads
rust-version in Cargo.toml, the floor
the maturin steps in wheels.yml and install.yml, which name the
version themselves because the manylinux and musllinux containers do
not read the toolchain file

No source change was needed. chunks_exact_to_as_chunks, the new 1.98
lint that broke tamnd/zu and tamnd/zu-node, has nothing to fire on
here.

Checked locally on 1.98.0:

cargo check --all-targets, cargo fmt --all --check, and
cargo clippy --all-targets -- -D warnings clean
both feature rows CI builds:
--no-default-features --features pyo3/extension-module and
--features abi3t,pyo3/extension-module
pytest: 780 passed, 5 skipped

tamnd/zu moved to 1.98.0 and toolchains.toml is what says which version every repository holds, so this follows it: the toolchain file, the manifest floor, and the two maturin jobs that name the version themselves because the build container does not read the toolchain file. Nothing in the source needed changing. The 1.98 lint that caught the other repositories, chunks_exact_to_as_chunks, has nothing to fire on here. cargo check, fmt and clippy with -D warnings are clean on 1.98 for the default features and for both of the feature rows CI builds, and pytest is 780 passed, 5 skipped.