# [1.0.0-beta.19](https://git.gitlab.arm.com/bazel/toolchain_utils/compare/v1.0.0-beta.18...v1.0.0-beta.19) (2024-12-04)

### Bug Fixes

* strip output of `uname -r` ([4de60581](https://git.gitlab.arm.com/bazel/toolchain_utils/commit/4de60581787b6ae1a8694d673080042ac8cc7bac))

Malte Poll authored Nov 23, 2024 and Matthew Clarkson committed Dec 04, 2024

I saw an isue where `uname -r` contains an extra newline on some
machines. This leads to the code trying to parse an int from
an invalid string:

Repository rule triplet defined at:
  /.../external/toolchain_utils~/toolchain/local/triplet/repository.bzl:33:26: in <toplevel>
ERROR: /.../external/toolchain_utils~/toolchain/local/triplet/os.bzl:126:82: An error occurred during the fetch of repository 'toolchain_utils~~_repo_rules~local':
   Traceback (most recent call last):
	File "/.../external/toolchain_utils~/toolchain/local/triplet/repository.bzl", line 24, column 25, in implementation
		triplet = detect(rctx).value
	File "/.../external/toolchain_utils~/toolchain/local/triplet/detect.bzl", line 11, column 11, in detect
		os(rctx).value,
	File "/.../external/toolchain_utils~/toolchain/local/triplet/os.bzl", line 181, column 22, in os
		return _uname(rctx, path)
	File "/.../external/toolchain_utils~/toolchain/local/triplet/os.bzl", line 126, column 82, in _uname
		return VersionedInfo("{}.{}.{}.{}".format(kernel, int(major), int(minor), int(patch)))
Error in int: invalid base-10 literal: "114\n"

# [1.0.0-beta.18](https://git.gitlab.arm.com/bazel/toolchain_utils/compare/v1.0.0-beta.17...v1.0.0-beta.18) (2024-11-20)

### Bug Fixes

* bump to `7.1.0+` due to `rctx.getenv` ([3228e100](https://git.gitlab.arm.com/bazel/toolchain_utils/commit/3228e1007aa69e9e6d41dc8cea0f57e3246b2501))
* **toolchain_local_select:** use `label_keyed_string_dict` for `map` attribute ([1d48d2e4](https://git.gitlab.arm.com/bazel/toolchain_utils/commit/1d48d2e43ff1cbe1d2746aa7c7b7b86363fad2a0))

### BREAKING CHANGES

* **toolchain_local_select:** `toolchain_local_select#map` is now flipped taking the labels as they keys rather than as the values.

Previous releases had the following setup:

```py
download_file(
    name = "abc-arm64-linux-gnu",
    output = "abc",
)

download_file(
    name = "abc-arm64-linux-musl",
    output = "abc",
)

toolchain_local_select(
    name = "abc",
    map = {
        "arm64-linux-gnu": "@abc-arm64-linux-gnu",
        "arm64-linux-musl": "@abc-arm64-linux-musl",
    },
)
```

This prevented eagarly overfetching all the repositories that would be
selected. As of Bazel 7.4.0+[1], it no longer overfetches so the `map`
attribute has been switched to a `label_keyed_string_dict`:

```py
toolchain_local_select(
    name = "abc",
    map = {
        "@abc-arm64-linux-gnu": "arm64-linux-gnu",
        "@abc-arm64-linux-musl": "arm64-linux-musl",
    },
)
```

The repository rule will _only_ fetch the repostory label that has been selected due
to the triplet value matching.

Whilst this is a breaking change, it will introduce a regression on Bazel 7.3 and below
which will overfetch the repositories. It is *highly* recommended to use Bazel 7.4 and above.

[1]: https://github.com/bazelbuild/bazel/commit/6fabb1fc6869a204373e5ee0adde696a659415dd

BREAKING CHANGE: `toolchain_local_select#map` is now flipped taking the labels as they keys rather than as the values.

Previous releases had the following setup:

```py
download_file(
    name = "abc-arm64-linux-gnu",
    output = "abc",
)

download_file(
    name = "abc-arm64-linux-musl",
    output = "abc",
)

toolchain_local_select(
    name = "abc",
    map = {
        "arm64-linux-gnu": "@abc-arm64-linux-gnu",
        "arm64-linux-musl": "@abc-arm64-linux-musl",
    },
)
```

This prevented eagarly overfetching all the repositories that would be
selected. As of Bazel 7.4.0+[1], it no longer overfetches so the `map`
attribute has been switched to a `label_keyed_string_dict`:

```py
toolchain_local_select(
    name = "abc",
    map = {
        "@abc-arm64-linux-gnu": "arm64-linux-gnu",
        "@abc-arm64-linux-musl": "arm64-linux-musl",
    },
)
```

The repository rule will _only_ fetch the repostory label that has been selected due
to the triplet value matching.

Whilst this is a breaking change, it will introduce a regression on Bazel 7.3 and below
which will overfetch the repositories. It is *highly* recommended to use Bazel 7.4 and above.

[1]: https://github.com/bazelbuild/bazel/commit/6fabb1fc6869a204373e5ee0adde696a659415dd

A rule is assigned the `kind` from the variable name.

This change makes sure that `rule` declarations have the correct `kind`.

Documentation strings are moved to global private variables as well.

# [1.0.0-beta.17](https://git.gitlab.arm.com/bazel/toolchain_utils/compare/v1.0.0-beta.16...v1.0.0-beta.17) (2024-10-28)

### Bug Fixes

* detect both `WORKSPACE` and `REPO.bazel` in repositories ([f1e46c3f](https://git.gitlab.arm.com/bazel/toolchain_utils/commit/f1e46c3f142c0665f90119996f0ebb8048dfb0c7))

When a repository label is passed, we validate that it **is**
a repository by checking for `REPO.bazel`.

To support back to `7.0.0` we can check for both `WORKSPACE` _and_ `REPO.bazel`.

# [1.0.0-beta.16](https://git.gitlab.arm.com/bazel/toolchain_utils/compare/v1.0.0-beta.15...v1.0.0-beta.16) (2024-10-21)

### Bug Fixes

* bump minimum Bazel version to `7.1.0` ([66d1a24d](https://git.gitlab.arm.com/bazel/toolchain_utils/commit/66d1a24dc741f55dc90df61da9a358ea10e3dc92))
* **libc/gnu:** add `2.{39,40}` versions ([d6221c91](https://git.gitlab.arm.com/bazel/toolchain_utils/commit/d6221c917e3f48594bbfcf3cdcc579b99651145a))
* **local:** correct failure message ([2c40116c](https://git.gitlab.arm.com/bazel/toolchain_utils/commit/2c40116c2c037e4c7b961a5a6c0c5aa6d842cffd))
* **local:** parse msys2 `uname` output ([bca66bb8](https://git.gitlab.arm.com/bazel/toolchain_utils/commit/bca66bb8cf8b96b374d149a04301c16d06f8c1af))
* switch to `REPO.bazel` from `WORKSPACE` ([0fbf9c6f](https://git.gitlab.arm.com/bazel/toolchain_utils/commit/0fbf9c6fd718736a6dc9c590b6657c5c0e693e7f))

### Features

* **local/triplet:** override detection with `BAZEL_TOOLCHAIN_UTILS_LOCAL_TRIPLET` ([d0c72342](https://git.gitlab.arm.com/bazel/toolchain_utils/commit/d0c72342657a67939d95371d725e2c79191a1942))

We need the `REPO.bazel` generation.

Ensures that we have the correct setup for Bazel commands
in `semantic-release`.

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

### Bug Fixes

* **resolved:** forward on `RunEnvironmentInfo` ([a41e8878](https://git.gitlab.arm.com/bazel/toolchain_utils/commit/a41e8878edfb0b9e71d3c504111a956bfd6ddc14))

# [1.0.0-beta.14](https://git.gitlab.arm.com/bazel/toolchain_utils/compare/v1.0.0-beta.13...v1.0.0-beta.14) (2024-09-06)

### Bug Fixes

* **local:** grab first part of `uname -r` ([e040928d](https://git.gitlab.arm.com/bazel/toolchain_utils/commit/e040928dc9ba3ba87e6feedbe3850d751a0896a2))
* **local:** provide `/etc/os-release` defaults ([177738d7](https://git.gitlab.arm.com/bazel/toolchain_utils/commit/177738d71b8b50b0c13a02c494f6cf04d93bd316))
* remove `ToolchainInfo#inherited` ([7608c42b](https://git.gitlab.arm.com/bazel/toolchain_utils/commit/7608c42b57f6c2b7b9db4b61aed54a3fc27557d7))

### Features

* add `//toolchain/constraint/local:{cpu,os,libc}` aliases ([a384e649](https://git.gitlab.arm.com/bazel/toolchain_utils/commit/a384e6491bbad9975e4cf9ce5e16758e8e6b7c01))
* add `//toolchain/local/constraint:{cpu,os,libc}` targets ([cf24d760](https://git.gitlab.arm.com/bazel/toolchain_utils/commit/cf24d7609f95b765698181a24a370fc4b5c160ac))
* add couplet platforms ([27ba292a](https://git.gitlab.arm.com/bazel/toolchain_utils/commit/27ba292a92948f25e8b429d25b463f47727c8597))

### BREAKING CHANGES

* `ToolchainInfo#inherited` removed

It is not possible to use these in an action as the host
environment variables cannot be read host environment variables.