# [1.0.0-alpha.6](https://git.gitlab.arm.com/bazel/rules_toolchain/compare/v1.0.0-alpha.5...v1.0.0-alpha.6) (2023-11-30)

### Bug Fixes

* add missing stub file ([fdcc9c01](https://git.gitlab.arm.com/bazel/rules_toolchain/commit/fdcc9c013c99bf6c0fb8c29270f4412f83400a83))
* upload release files to generic package registry ([d5deccfa](https://git.gitlab.arm.com/bazel/rules_toolchain/commit/d5deccfa9dc35482c23b7376fb368f8037d51845))

### Features

* add `export` extension ([35bae073](https://git.gitlab.arm.com/bazel/rules_toolchain/commit/35bae07323b7ac4a9ddeab60909d9c411970fab2))
* **rules_toolchain:** add `:entrypoint` target to local repositories ([a995bd47](https://git.gitlab.arm.com/bazel/rules_toolchain/commit/a995bd4702de985b14cd99ce1f896f1833342b29))

Allows access with a GitLab API token.

Normal release assets need a UI login.

This is important to provide a consistent target for resolving hermetic tools in repository rules.

For example, one can use a local tool as so:

```py
local(name = "echo")
something(echo = "@echo//:entrypoint")
```

Later, one can switch out the local entrypoint for a hermetically downloaded tool.

In the future, we may provide a `toolchain_entrypoint` repository rule that provides an
entrypoint that understands how to correctly setup `LD_LIBRARY_PATH` (and similar).

This is helpful when using pre-built binaries from package repositories that are linked
dynamically:

```py
download_deb(name = "unionfs", ...)
download_deb(name = "fuse", ...)
toolchain_entrypoint(
    name = "unionfs",
    libraries = [
        "@fuse//:usr/lib/libfuse.so",
    ],
)
```

Follows the common convention of prefixing public exports in `defs.bzl`

The extension can be use to "export" local repositories into the extension.

This is especially useful for exposing repositories that provide hermetic, executable entrypoints.

# [1.0.0-alpha.5](https://git.gitlab.arm.com/bazel/rules_toolchain/compare/v1.0.0-alpha.4...v1.0.0-alpha.5) (2023-11-16)

### Bug Fixes

* **release:** tidy up `metadata.json` naming in GitLab UI ([d5029b95](https://git.gitlab.arm.com/bazel/rules_toolchain/commit/d5029b95ddd3cda4556bad52f2b985df0abdc23b))

# [1.0.0-alpha.4](https://git.gitlab.arm.com/bazel/rules_toolchain/compare/v1.0.0-alpha.3...v1.0.0-alpha.4) (2023-11-16)

### Bug Fixes

* **release:** add `metadata.json` to the release ([d8557b55](https://git.gitlab.arm.com/bazel/rules_toolchain/commit/d8557b55d92bdba0adb4724278842868daa09430))

# [1.0.0-alpha.3](https://git.gitlab.arm.com/bazel/rules_toolchain/compare/v1.0.0-alpha.2...v1.0.0-alpha.3) (2023-11-16)

### Bug Fixes

* **release:** correct source archive upload ([05f5f208](https://git.gitlab.arm.com/bazel/rules_toolchain/commit/05f5f208f15461ad28bcc3699ce9a8d6c838121a))

`@semantic-release/config-gitlab-bzlmod` has the fixes.

# [1.0.0-alpha.2](https://git.gitlab.arm.com/bazel/rules_toolchain/compare/v1.0.0-alpha.1...v1.0.0-alpha.2) (2023-11-16)

### Bug Fixes

* **resolved:** forward on `basename` attribute ([e71e807b](https://git.gitlab.arm.com/bazel/rules_toolchain/commit/e71e807b6ded13a3baf2d430900f675a1f8849fd))
* **test:** correctly output `stderr` from toolchain executable on error ([22cd1081](https://git.gitlab.arm.com/bazel/rules_toolchain/commit/22cd108126e8917d7142d7f447fdc61f69ea2521))

### Features

* **local_which:** make local binaries non-mandatory ([5d9a292c](https://git.gitlab.arm.com/bazel/rules_toolchain/commit/5d9a292cfd4a7f9dd5b952ca33c34b01da0fc796))

This allows the implicit `:resolved` target to be used even when the
local binary is not provided.

Technically, we can avoid that because one could set up both `local`
_and_ `resolved` repository rules. That is a boilerplate pain though.

This moves the error to execution time which is a bit of a pain.

Previously, because the repository was only resolved when a target
explicitly requested the local toolchain the error would be caught
before execution time. However, moving the convenience `:resolved`
target into the `local` repository nullifies that because the
repository needs to be resolved for _any_ toolchain because the
`:resolved` target is re-used.

The trade-off here seems worth it for simple `MODULE.bazel`
repository definitions.

Allows setting up resolved toolchains for multi-call binaries.

Implements a nice label in the release page for the source archive.

# 1.0.0-alpha.1 (2023-11-15)

### Bug Fixes

* correct executable permissions of repository files ([7e3b5863](https://git.gitlab.arm.com/bazel/rules_toolchain/commit/7e3b58635c7c375269e1643195f0a829ec59dcf1))
* **rules_toolchain:** add `amd64`/`arm64` aliases ([332bb9b8](https://git.gitlab.arm.com/bazel/rules_toolchain/commit/332bb9b839176d7ad211f7e2f499b80716d37500))
* **rules_toolchain:** add `no-remote` to local binary symlinks ([254a3d5d](https://git.gitlab.arm.com/bazel/rules_toolchain/commit/254a3d5d9c78772ffc681f7e5ea099e754bbb3b9))
* **rules_toolchain:** add `x86_64`/`aarch64` CPU targets ([bed57561](https://git.gitlab.arm.com/bazel/rules_toolchain/commit/bed5756126fa64764d80a61cb78afada41d09de0))
* **rules_toolchain:** add locally detect OS version to constraints ([a1eae556](https://git.gitlab.arm.com/bazel/rules_toolchain/commit/a1eae55624fb1b2253a3c254943dddb3a98ddc3b))
* **rules_toolchain:** all multiple files to `symlink` ([843f6cc7](https://git.gitlab.arm.com/bazel/rules_toolchain/commit/843f6cc729a213a6d367f54bd11d9d8f87daf842))
* **rules_toolchain:** correct GNU libc check ([1689f920](https://git.gitlab.arm.com/bazel/rules_toolchain/commit/1689f9201b70e6f9a22bebb879d67175421d51a3))
* **rules_toolchain:** do a better job of processing `/etc/release` ([561463ab](https://git.gitlab.arm.com/bazel/rules_toolchain/commit/561463ab90b43341d4f0b66145a3816d64231c41))
* **rules_toolchain:** local binary not found error ([eb0dcd8b](https://git.gitlab.arm.com/bazel/rules_toolchain/commit/eb0dcd8b3ea19c7a414486a6a1e00935ebee6a32))
* **rules_toolchain:** only expose unversioned triplets ([6f607646](https://git.gitlab.arm.com/bazel/rules_toolchain/commit/6f6076467613bba30c3bdefe92a7450d266c60c4))
* **rules_toolchain:** respect `target` attribute ([b5773053](https://git.gitlab.arm.com/bazel/rules_toolchain/commit/b577305399516eaf21d341cf7e687a25ef20ed68))
* **rules_toolchain:** simplify Bazel run commands ([cb5ae502](https://git.gitlab.arm.com/bazel/rules_toolchain/commit/cb5ae5022da29042416443699c82a65d3fdfd955))
* **rules_toolchain:** support no legacy runfiles ([fdc609e4](https://git.gitlab.arm.com/bazel/rules_toolchain/commit/fdc609e4aeda92fadf8c1154b0f012556cdfb133))

### Features

* add a `resolved` target to local binary repositories ([7ad98062](https://git.gitlab.arm.com/bazel/rules_toolchain/commit/7ad98062778c17c7b143a2a366b18361ba950d09))
* **rules_toolchain:** add `DataInfo.executable` ([6cc16f24](https://git.gitlab.arm.com/bazel/rules_toolchain/commit/6cc16f24832cd3b1948929d52fb738d76be90f2c))
* **rules_toolchain:** add `echo` toolchain end-to-end test ([9309dd1a](https://git.gitlab.arm.com/bazel/rules_toolchain/commit/9309dd1acd992fe6be15faaef180a43febcc94c0))
* **rules_toolchain:** add `host` platform and constraint ([9f8ae2c7](https://git.gitlab.arm.com/bazel/rules_toolchain/commit/9f8ae2c728914d7d8adbed93c75338e962ffdd2f))
* **rules_toolchain:** add `local.select` extension ([97b4386f](https://git.gitlab.arm.com/bazel/rules_toolchain/commit/97b4386fdbc416ba7b2b701ac6a56f1ed9abf187))
* **rules_toolchain:** add `toolchain_symlink_path` rule ([f03782a0](https://git.gitlab.arm.com/bazel/rules_toolchain/commit/f03782a088727dba597915d65aa83ed8830eb87b))
* **rules_toolchain:** add `toolchain_symlink_target` rule ([f8987a49](https://git.gitlab.arm.com/bazel/rules_toolchain/commit/f8987a4989363331142df10bce7b6269456da14f))
* **rules_toolchain:** add `toolchain_test` rule ([550b3b1f](https://git.gitlab.arm.com/bazel/rules_toolchain/commit/550b3b1fc183bed745366320ba26632ecb055f9f))
* **rules_toolchain:** add `uname` release detection ([23260b3b](https://git.gitlab.arm.com/bazel/rules_toolchain/commit/23260b3baa8d6e157390e6656dea2309454017cd))
* **rules_toolchain:** add customising the basename for symlink rules ([9ad523df](https://git.gitlab.arm.com/bazel/rules_toolchain/commit/9ad523dfe0e31f0c5bdf17163741befca139e519))
* **rules_toolchain:** add extension for finding local binaries ([2ed07d3b](https://git.gitlab.arm.com/bazel/rules_toolchain/commit/2ed07d3b5ec30b7fceac760c6249d6a9f35bc15d))
* **rules_toolchain:** add host triplet detection ([0e2e2116](https://git.gitlab.arm.com/bazel/rules_toolchain/commit/0e2e211668df6fc8af0ccb0fe1e6bf4ac25566c4))
* **rules_toolchain:** add local toolchain information rule ([d6b279dc](https://git.gitlab.arm.com/bazel/rules_toolchain/commit/d6b279dc9aeb5522746d944b3ee59ae6ae3f067d))
* **rules_toolchain:** add triplet constraints ([52205111](https://git.gitlab.arm.com/bazel/rules_toolchain/commit/522051114a772fb7a878e5f6df44446c944dcba6))
* **rules_toolchain:** add triplet platforms ([14aba1de](https://git.gitlab.arm.com/bazel/rules_toolchain/commit/14aba1de9d9c97ab71b49c2a832960ed64640d7e))
* **rules_toolchain:** add triplet targets and information ([61871330](https://git.gitlab.arm.com/bazel/rules_toolchain/commit/6187133091be4f6f6fc5b24444d380033ba244eb))
* **rules_toolchain:** expose `glibc` `VERSIONS` collection ([5db2957e](https://git.gitlab.arm.com/bazel/rules_toolchain/commit/5db2957e727342dfc00e000c34310b1a08a1f088))
* **rules_toolchain:** generate LTS version variants ([6deceb46](https://git.gitlab.arm.com/bazel/rules_toolchain/commit/6deceb4619a4a0fd04565d2403ac60297eeae931))
* **rules_toolchain:** generate versioned triplets ([63c94365](https://git.gitlab.arm.com/bazel/rules_toolchain/commit/63c943658fdce7fbb7a151374c60bdb615261da2))
* **rules_toolchain:** test anything protocol for testing ([191ce97e](https://git.gitlab.arm.com/bazel/rules_toolchain/commit/191ce97e2c613e849f803dc1c7ff958f0ff9f021))

This removes the need for a custom `resolved` rule for every toolchain.

Upgrade path is to add the `toolchain_type` to the local repository
rule in `MODULE.bazel` and change the `resolved` target to an alias.

A `toolchain_resolved` repository rule is added as well for toolchains
that do not use local binaries.

This patch hugely simplifies the creation of toolchains downstream.

The default is to set files as executable in repository rules.

We often do not want that.