# [1.0.0-beta.8](https://git.gitlab.arm.com/bazel/ape/compare/v1.0.0-beta.7...v1.0.0-beta.8) (2024-06-17)

### Bug Fixes

* **upload:** bump to `rules_curl@1.0.0-alpha.8` ([46be5506](https://git.gitlab.arm.com/bazel/ape/commit/46be5506f8c2fe37a4d2bc649f1abb47c9f875fb))

### Features

* add `//:assimilate` ([4a43c390](https://git.gitlab.arm.com/bazel/ape/commit/4a43c3907740218bebcda4c6c5c6f1bc26c63c32))
* add `ape_assimilate` rule ([0ffc0247](https://git.gitlab.arm.com/bazel/ape/commit/0ffc02472fac8cd93db0daa393fab072c5864e68))
* switch to assimilated binaries ([def09160](https://git.gitlab.arm.com/bazel/ape/commit/def09160eeaeba44a59717b23a04ac626584e2b9))

Assimilated binaries are converted from a "fat" APE into a native
binary for the provided host.

This change means that the APE binaries are completely hermetic
binaries that do not require their own launcher, shell script or
anything else.

This solves a huge bootstrapping problem that POSIX shell scripts
need runfiles but to effectively find the runfiles one needs POSIX
tooling to resolve symlinks, etc.

Having a single executable to rely on solves the need for runfiles.

This rule takes a APE binary and turns it into a native binary.

This can be used to convert a APE into a native binary

Fixes hermeticity and runfiles issues with `curl`.

# [1.0.0-beta.7](https://git.gitlab.arm.com/bazel/ape/compare/v1.0.0-beta.6...v1.0.0-beta.7) (2024-05-22)

### Bug Fixes

* correct `ape-m1.c` upstream URL ([db0cb832](https://git.gitlab.arm.com/bazel/ape/commit/db0cb83293d1ef9df91882e71dfba8007dd2a7ad))
* rolled back `pigz` version ([6d098c8a](https://git.gitlab.arm.com/bazel/ape/commit/6d098c8a6b80b86eda05c25996927e207c9878d8))

### Features

* add `chmod`/`cp`/`dd`/`echo`/`gzip`/`mkdir`/`mv`/`printf`/`rm`/`uname` ([b312d301](https://git.gitlab.arm.com/bazel/ape/commit/b312d30110dda67426e6db2e124a1c316340ec2b))

Thomas Wilks authored May 21, 2024 and Matthew Clarkson committed May 22, 2024

`pigz` is being downgraded because with the current version decompression
fails[1]:

```sh
$ curl -sLf https://github.com/ahgamut/superconfigure/releases/download/z0.0.39/compress.zip -o compress.zip
$ unzip compress.zip
$ echo "Hello, world" > hello-world.txt
$ ./bin/pigz hello-world.txt
$ ./bin/pigz -cdkv hello-world.txt.gz --stdout > hello-world.txt~
(segmentation fault)
```

The `3.2.4` binary worked fine, so we are rolling back to that for now.

When a new version of `cosmos` binaries have been released, we should
check that the decompression works and upgrade.

[1]: https://github.com/ahgamut/superconfigure/issues/38

There have been no changes between `3.3.1` and `3.3.3` so the integrity
is identical.

# [1.0.0-beta.6](https://git.gitlab.arm.com/bazel/ape/compare/v1.0.0-beta.5...v1.0.0-beta.6) (2024-05-07)

### Bug Fixes

* **binary:** find external runfiles on Windows ([a6a8df04](https://git.gitlab.arm.com/bazel/ape/commit/a6a8df04ed1181c30c01d68e6ef1b9e5512c1374))

# [1.0.0-beta.5](https://git.gitlab.arm.com/bazel/ape/compare/v1.0.0-beta.4...v1.0.0-beta.5) (2024-05-04)

### Bug Fixes

* upgrade to `toolchain_utils@1.0.0-beta.9` ([246b23be](https://git.gitlab.arm.com/bazel/ape/commit/246b23be38f24f24b360a4649a1f55706f5b651f))

Requires a change to `toolchain_info` rule to get access to
`ToolchainInfo#run` which provides `FilesToRunInfo`. This can
be used to correctly expose the runfiles to a n action.

When running on `arm64` executors the following error occurs:

```
../ape~1.0.0-beta.4/ape/toolchain/ape/ape-arm64-linux/ape-arm64-linux: 1: ../ape~1.0.0-beta.4/ape/toolchain/ape/ape-arm64-linux/ape-arm64-linux: Syntax error: "(" unexpected
```

This may be due to the executors having a custom `binfmt_misc` setup.

It needs more debugging but we can force AMD64 executors for now.

# [1.0.0-beta.4](https://git.gitlab.arm.com/bazel/ape/compare/v1.0.0-beta.3...v1.0.0-beta.4) (2024-05-01)

### Bug Fixes

* **binary:** correct visibility of binary template ([3f33ed44](https://git.gitlab.arm.com/bazel/ape/commit/3f33ed44a93cc4c5405416b366752c817ba45da9))

# [1.0.0-beta.3](https://git.gitlab.arm.com/bazel/ape/compare/v1.0.0-beta.2...v1.0.0-beta.3) (2024-05-01)

### Bug Fixes

* **ape.pe:** implement a C# launcher ([4f667dd8](https://git.gitlab.arm.com/bazel/ape/commit/4f667dd858d683e43176d538797931f52b39f036))
* **entrypoint:** remove toolchain target ([d9d60dc2](https://git.gitlab.arm.com/bazel/ape/commit/d9d60dc262dafe669e661bc48f339f77322f4a6c))
* make `@ape//:*` binaries remote execution friendly ([7ae62935](https://git.gitlab.arm.com/bazel/ape/commit/7ae62935125b5e72ccaab248bc3a73b927901403))

### Features

* add `//ape/toolchain/ape:type` ([3e73cdb6](https://git.gitlab.arm.com/bazel/ape/commit/3e73cdb63c21caede525321dc8f797ec9fcc1945))
* add `ape_binary` rule ([6577cd36](https://git.gitlab.arm.com/bazel/ape/commit/6577cd36eeaf814b38a66a3c1fbd1e7ce218f1e6))

### BREAKING CHANGES

* **entrypoint:** The `toolchain_symlink_target` has been removed from `ape_entrypoint`.

This symlink target used the repository context entrypoint which is not remote execution
friendly.

The targets were aliased as `@ape//:*` which have been corrected to be remove execution
friendly. Use those targets instead.

Running the APE launcher on `aarch64` instances can fail with:

```
ape/toolchain/ape/ape-arm64-linux/ape-arm64-linux: 1: ape/toolchain/ape/ape-arm64-linux/ape-arm64-linux: Syntax error: "(" unexpected
```

This may be a `binfmt_misc` issue that is interpreting the binary incorrectly.

More investigation is needed.

For now, we will disable remote execution.

BREAKING CHANGE: The `toolchain_symlink_target` has been removed from `ape_entrypoint`.

This symlink target used the repository context entrypoint which is not remote execution
friendly.

The targets were aliased as `@ape//:*` which have been corrected to be remove execution
friendly. Use those targets instead.

# [1.0.0-beta.2](https://git.gitlab.arm.com/bazel/ape/compare/v1.0.0-beta.1...v1.0.0-beta.2) (2024-04-25)

### Bug Fixes

* support for MinGW shell ([76a064cb](https://git.gitlab.arm.com/bazel/ape/commit/76a064cb9299d6b66d6874d786f59509e78ee1ea))

`toolchain_utils@1.0.0-beta.6` learnt support for detecting the host
on the MinGW shell. Bumping to that version gains support here.