# [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.

# 1.0.0-beta.1 (2024-04-24)

### Bug Fixes

* correct PE launcher target ([3af329c6](https://git.gitlab.arm.com/bazel/ape/commit/3af329c66df8c38e7cfce3478dc61862be49d684))
* mirror binaries ([b6b4b780](https://git.gitlab.arm.com/bazel/ape/commit/b6b4b780e211707ed14d9d466571ba7bd3fab0a7))
* register toolchains for supported platforms ([37883016](https://git.gitlab.arm.com/bazel/ape/commit/3788301606765c37ad6f22ebb01d86168319d355))

### Features

* add `ape_toolchain` macro ([e89d679e](https://git.gitlab.arm.com/bazel/ape/commit/e89d679e18822f90ac64f14479932b0477ee8239))
* add `diff`, `diff3`, `sdiff`, `cmp` and `patch` ([a49565d5](https://git.gitlab.arm.com/bazel/ape/commit/a49565d57425470e12d74a42e1f481bb70543ded))
* add `exec_compatible_with` to `ape_toolchain` ([fee2332c](https://git.gitlab.arm.com/bazel/ape/commit/fee2332c067c7ee065fc14f15de86408fe8cd56a))
* added semantic release to bazel template ([a8a66341](https://git.gitlab.arm.com/bazel/ape/commit/a8a663411461dfd66fcc36635b1659a1beb3bd6b))
* expose `cosmo@v3.2.4` binaries ([c8dd4cbc](https://git.gitlab.arm.com/bazel/ape/commit/c8dd4cbc64cd6c213b5f4bf73279b7b265d06f8c))
* support Apple silicon ([8725298c](https://git.gitlab.arm.com/bazel/ape/commit/8725298cf9dddb7fbc40c466a7fcb403eb8dd7a5))
* upgrade to `cosmos@3.3.1` ([eb9f860f](https://git.gitlab.arm.com/bazel/ape/commit/eb9f860f207ae8ccdea93ce637b0e5305a99fb14))

Removes need to download directly from `superconfigure` for `diff` and `patch` projects.

Allows adding extra constraints to the execution platform.

https://github.com/jart/cosmopolitan/wiki/Features#systems-and-cpu-arch-supported

The macro registers APE binaries for the platform contraints that are supported.

This prevents host platforms that are unsupported from resolving the toolchain.

```py
load("@ape//ape/toolchain:defs.bzl", "ape_toolchain")

toolchain_type(
    name = "type",
)

ape_toolchain(
    name = "ape",
    toolchain = "@ape//:curl",
    toolchain_type = ":type",
)
```

We need a second maintainer for each section!

This patch adds `upload:*` targets to the project that will upload the
binaries and put them in the GitLab generic package registry.

This requires a `~/.netrc` with a `api` token setup for `gitlab.arm.com`.

To upload all binaries perform the following:

    for TARGET in $(bazelisk query 'upload:*'); do
        bazelisk run --ui_event_filters -INFO -- "${TARGET}"
    done

Things to do in the future:

- Create a `multirun` upload target that does the upload in parallel
- Add a manually triggered CI job that does the upload
  - This will need a deploy token with _only_ package registry access

For now, a manual upload has been done help with outages.