# [1.0.0-beta.16](https://git.gitlab.arm.com/bazel/ape/compare/v1.0.0-beta.15...v1.0.0-beta.16) (2024-11-27)

### Bug Fixes

* bump minimum version to Bazel `7.4.0` ([bf86a08c](https://git.gitlab.arm.com/bazel/ape/commit/bf86a08cc9775c710e5be3dff31b566976826ba5))

Needed to avoid overfetching and attempting to fetch `zig`
on `non-arm64-macos-darwin` devices.

# [1.0.0-beta.15](https://git.gitlab.arm.com/bazel/ape/compare/v1.0.0-beta.14...v1.0.0-beta.15) (2024-11-20)

### Bug Fixes

* make `@ape//:*` targets private ([1f9ebb25](https://git.gitlab.arm.com/bazel/ape/commit/1f9ebb2549b67f08542e9f2b5f59349a8d000fae))
* switch `toolchain_local_select#map` to lazily fetch labels ([292d222b](https://git.gitlab.arm.com/bazel/ape/commit/292d222b42ea54837ff049b9bce1146a96197515))

These have been deprecated for a few releases and were badly
named. These targets are now under `@ape//ape/toolchain/info:*` targets. `@ape//ape:*` targets are `exec`/`target` configuration flexible.

# [1.0.0-beta.14](https://git.gitlab.arm.com/bazel/ape/compare/v1.0.0-beta.13...v1.0.0-beta.14) (2024-10-30)

### Bug Fixes

* upgrade `toolchain_utils@1.0.0-beta.17` for Bazel 8+ support ([798f0612](https://git.gitlab.arm.com/bazel/ape/commit/798f06125affc958172882443f827c4a9194311b))

### Features

* upgrade to `3.7.1` binaries ([ac2753e1](https://git.gitlab.arm.com/bazel/ape/commit/ac2753e15fbef915ee3ecdd220efe76201e4e2fd))

# [1.0.0-beta.13](https://git.gitlab.arm.com/bazel/ape/compare/v1.0.0-beta.12...v1.0.0-beta.13) (2024-07-26)

### Bug Fixes

* **ape_toolchain:** make `toolchain_utils` constraints relative to `[@ape](https://git.gitlab.arm.com/ape)` module ([69001a59](https://git.gitlab.arm.com/bazel/ape/commit/69001a59b44c7618fc04f51ae741a884710daa60))

# [1.0.0-beta.12](https://git.gitlab.arm.com/bazel/ape/compare/v1.0.0-beta.11...v1.0.0-beta.12) (2024-07-22)

### Bug Fixes

* **assimilate:** make rule public ([d4b1be09](https://git.gitlab.arm.com/bazel/ape/commit/d4b1be09d711defd822cb581c43674924e04e656))
* **binary:** make rule public ([793c0f2e](https://git.gitlab.arm.com/bazel/ape/commit/793c0f2e83b3f95ce7b147d6fc65c2a9c3c07d79))
* **entrypoint:** add `local = True` ([699fcb6c](https://git.gitlab.arm.com/bazel/ape/commit/699fcb6c036b94a3505d4231ee522daafbb4391d))
* **entrypoint:** assimilate on Linux ([b4ff17be](https://git.gitlab.arm.com/bazel/ape/commit/b4ff17be88820667fd85fb37283e0e5d06130087))

### Features

* add `@ape//ape/toolchain/info:*` targets ([c767ec08](https://git.gitlab.arm.com/bazel/ape/commit/c767ec08894e1874cd183ffe99e76c4f25e1bc86))
* make `@ape//ape:*` targets publically visible ([4978c177](https://git.gitlab.arm.com/bazel/ape/commit/4978c177fd073b18eec3e600a5a2fe1e26f5b5f8))

Allows downstream users to select a `target` configuration
compatible APE target.

The `@ape//:*` targets are explicitly for the `exec` configuration.

This has lead to confusion when selecting a APE binary target that is needed
for the `target` configuration.

New `@ape//ape/toolchain/info` targets have been added to make the target name
explicit. A toolchain will _always_ be for the execution platform.

This rule only depends on local data so can be marked as such.

If a Linux user has Wine installed with the `binfmt_misc` registration,
an APE binary is picked up and ran under the Wine runtime.

Normally, this does not occur, as we force execution under the launcher.

However, Python `sys.executable` will return the original binary so
any Python script that uses `sys.executable` with `subprocess` will
unexpectedly run under Wine.

Assimilating the binary on Linux avoids this situation. In all other cases
we can symlink to the binary.

# [1.0.0-beta.11](https://git.gitlab.arm.com/bazel/ape/compare/v1.0.0-beta.10...v1.0.0-beta.11) (2024-06-18)

### Bug Fixes

* **assimilate:** ensure Windows executable extension ([4e636524](https://git.gitlab.arm.com/bazel/ape/commit/4e636524a5cfa246a24d8478d2c2f2494fee0983))

This tags targets which cannot build on every platform and
run targets that are unnecessary to build as part of a
recursive build.

We need to make sure our APE binary targets work when symlinked.

The shift to assimilated binaries removes the need for runfiles.

The test will pass with assimilated binary targets.