v0.4.8

Release Channel Migration

Starting with this release, Hurry is distributed via GitHub Releases instead of AWS S3. The installation commands remain the same—just run:

curl -sSfL https://hurry.build/install.sh | bash

Changes in v0.4.8

Note

The version jump from v0.1.0 reflects releases that were previously distributed via S3. You can view the full changelog here if desired: v0.1.0...v0.4.8

• fix(hurry): Filter units with incomplete dependency chains by @jssblck in #327
• chore: Migrate releases from S3 to GitHub Releases by @jssblck in #325

Full Changelog: v0.4.7...v0.4.8

---

What is Hurry?

Hurry accelerates Cargo builds by intelligently caching and restoring build artifacts. It's a drop-in replacement that examines your build plan, restores cached artifacts from a shared cache, runs the build, and uploads new artifacts for your team.

# Instead of `cargo build`:
HURRY_API_TOKEN=your_token hurry cargo build

Distributed Build Cache

Share compiled artifacts across your team and CI. When a teammate or CI job compiles a dependency, everyone benefits—no redundant compilation.

Cross-Compilation Support

Building for a different target? Hurry accelerates cross-compilation via the cross tool:

hurry cross build --target aarch64-unknown-linux-gnu

Self-Hosting

Run your own Hurry API server on your infrastructure with the self-hosting guide. Full control over your build cache.

Platform Support

Platform	Build Acceleration
macOS (Intel & Apple Silicon)	✓ Full support
Linux x86_64/ARM64 (glibc)	✓ Full support
Linux x86_64/ARM64 (musl)	✓ Supported
Windows x86_64	Passthrough (coming soon)

---

Get started at hurry.build or check the README for details.