rattler-build 0.72.0

[BrewTestBot]

Created by brew bump

---

Created with brew bump-formula-pr.

Details

release notes

## [0.72.0] - 2026-07-28
### ✨ Highlights
This release introduces experimental build.steps as an alternative to build.script: each step is an isolated section of the build wrapper with its own if condition, interpreter, cwd, and env, so shell state no longer leaks between steps. It requires --experimental and is mutually exclusive with script. Recipes may now also carry a top-level $schema field for editor validation, and the process-execution layer gains reusable Runner and Session interfaces. Fixes cover case-insensitive RuntimeEnv lookups on Windows, deletion-only patches, Android DT_RUNPATH handling, and CEP-17 site-packages paths in SP_DIR.
Added

Add experimental build steps by @baszalmstra in #2646
Allow $schema top-level field in recipe.yaml by @bollwyvl in #2645
Support steps in staging outputs by @baszalmstra in #2647
Add Runner and Session execution interfaces by @baszalmstra in #2696

Fixed

Ignore case when querying variables from RuntimeEnv on Windows by @paperchalice in #2676
Deletion-only patches misdetected as already applied by @wolfv in #2695
Use CEP-17 path for SP_DIR by @wolfv in #2700
Use DT_RUNPATH instead of DT_RPATH on Android by @wolfv in #2699

Refactor

Extract pure resolve_process_env by @baszalmstra in #2677
Split process spawn from output handling by @baszalmstra in #2690
Rename NativeShellRunner to ShellDialect by @baszalmstra in #2692
Add an execution view for Directories by @baszalmstra in #2694
Inject RuntimeEnv into script environment generation by @baszalmstra in #2691

New Contributors

@paperchalice made their first contribution in #2676

View the full release notes at https://github.com/prefix-dev/rattler-build/releases/tag/v0.72.0.

---

[github-actions]

🤖 An automated task has requested bottles to be published to this PR.

Caution

Please do not push to this PR branch before the bottle commits have been pushed, as this results in a state that is difficult to recover from. If you need to resolve a merge conflict, please use a merge commit. Do not force-push to this PR branch.