build-release

• Docker with remote context truenas configured (pre-AVX-512 server)
• Local AVX-512 capable CPU for AVX-512 builds
• Current branch pushed to origin

```bash

# Set version

export VERSION=X.Y.Z

# Build remote binaries (AVX2, Vulkan, Parakeet-AVX2, Parakeet-CUDA)

docker context use truenas

docker compose -f docker-compose.build.yml build --no-cache avx2 vulkan parakeet-avx2 parakeet-cuda

docker run --rm -v $(pwd)/releases/${VERSION}:/output voxtype-parakeet-avx2

docker run --rm -v $(pwd)/releases/${VERSION}:/output voxtype-parakeet-vulkan

docker run --rm -v $(pwd)/releases/${VERSION}:/output voxtype-parakeet-parakeet-avx2

docker run --rm -v $(pwd)/releases/${VERSION}:/output voxtype-parakeet-parakeet-cuda

# Build local AVX-512 binaries

docker context use default

cargo clean && cargo build --release

cp target/release/voxtype releases/${VERSION}/voxtype-${VERSION}-linux-x86_64-avx512

cargo clean && RUSTFLAGS="-C target-cpu=native" cargo build --release --features parakeet

cp target/release/voxtype releases/${VERSION}/voxtype-${VERSION}-linux-x86_64-parakeet-avx512

# Verify versions

for bin in releases/${VERSION}/voxtype-*; do echo "$(basename $bin): $($bin --version)"; done

# Generate checksums

cd releases/${VERSION} && sha256sum voxtype-* > SHA256SUMS

# Create pre-release

gh release create v${VERSION} --prerelease --target BRANCH releases/${VERSION}/*

```

To avoid prompts during the build process, add these to your allowed commands:

```

• tool: Bash

prompt: switch docker context

• tool: Bash

prompt: build docker images

• tool: Bash

prompt: run docker containers

• tool: Bash

prompt: copy docker container files

• tool: Bash

prompt: cargo build

• tool: Bash

prompt: copy binaries

• tool: Bash

prompt: verify binary versions

• tool: Bash

prompt: generate checksums

• tool: Bash

prompt: create github release

• tool: Bash

prompt: git push

```

1. Prepare Version

Ensure Cargo.toml is updated and committed:

```bash

# Edit Cargo.toml with new version

cargo build # Updates Cargo.lock

git add Cargo.toml Cargo.lock

git commit -S -m "Bump to vX.Y.Z"

git push

```

2. Build Remote Binaries (AVX2, Vulkan, Parakeet)

These builds use Ubuntu 22.04 to avoid AVX-512 instruction contamination:

```bash

export VERSION=X.Y.Z

docker context use truenas

mkdir -p releases/${VERSION}

# Build all Docker images (takes ~10-15 min)

docker compose -f docker-compose.build.yml build --no-cache avx2 vulkan parakeet-avx2 parakeet-cuda

# Extract binaries from images

for service in avx2 vulkan; do

docker run --rm -v $(pwd)/releases/${VERSION}:/output voxtype-parakeet-${service}

done

docker run --rm -v $(pwd)/releases/${VERSION}:/output voxtype-parakeet-parakeet-avx2

docker run --rm -v $(pwd)/releases/${VERSION}:/output voxtype-parakeet-parakeet-cuda

```

3. Build Local AVX-512 Binaries

AVX-512 builds require a host CPU with AVX-512 support:

```bash

docker context use default

# Whisper AVX-512

cargo clean && cargo build --release

cp target/release/voxtype releases/${VERSION}/voxtype-${VERSION}-linux-x86_64-avx512

# Parakeet AVX-512

cargo clean && RUSTFLAGS="-C target-cpu=native" cargo build --release --features parakeet

cp target/release/voxtype releases/${VERSION}/voxtype-${VERSION}-linux-x86_64-parakeet-avx512

```

4. Verify All Binaries

```bash

for bin in releases/${VERSION}/voxtype-*; do

echo -n "$(basename $bin): "

$bin --version

done

```

All binaries must report the same version. If any differ, the Docker cache is stale.

5. Generate Checksums

```bash

cd releases/${VERSION}

sha256sum voxtype-* > SHA256SUMS

cat SHA256SUMS

```

6. Create GitHub Release

```bash

gh release create v${VERSION} \

--title "vX.Y.Z: Title" \

--prerelease \

--target BRANCH \

releases/${VERSION}/*

```

Wrong binary version

Docker caches aggressively. Rebuild with --no-cache:

```bash

docker compose -f docker-compose.build.yml build --no-cache avx2 vulkan

```

Remote build output missing

If docker compose up shows old binaries, the containers are stale. Use docker run to run fresh containers from the new images.

AVX-512 contamination in AVX2 binary

Check with objdump:

```bash

objdump -d releases/${VERSION}/voxtype-*-avx2 | grep -c zmm

```

Should be 0. If not, rebuild on a pre-AVX-512 host.

After successful build, releases/${VERSION}/ should contain:

```

voxtype-X.Y.Z-linux-x86_64-avx2

voxtype-X.Y.Z-linux-x86_64-avx512

voxtype-X.Y.Z-linux-x86_64-vulkan

voxtype-X.Y.Z-linux-x86_64-parakeet-avx2

voxtype-X.Y.Z-linux-x86_64-parakeet-avx512

voxtype-X.Y.Z-linux-x86_64-parakeet-cuda

SHA256SUMS

```