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

### Bug Fixes

* add support for `--incompatible_use_plus_in_repo_names` ([fc7d4858](https://git.gitlab.arm.com/bazel/toolchain_utils/commit/fc7d485887292676b5a87eb51c40f92aa6343b6b))

It was [found][1] the `~` character slows down C/C++ includes on Windows.

Bazel 8 will change to the `+` symbol.

The [--incompatible_use_plus_in_repo_names][2] flag allows testing this early.

This patch supports any separator.

[1]: https://github.com/bazelbuild/bazel/issues/22865
[2]: https://github.com/bazelbuild/bazel/issues/23127

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

### Features

* **info:** forward on `RunEnvironmentInfo` through `ToolchainInfo` ([08baa79e](https://git.gitlab.arm.com/bazel/toolchain_utils/commit/08baa79e8464d31cfaaa24ad199cde0a819f1d64))

Allows downstream toolchain consumers to export the environment variables.

It is always enabled on Bazel 7+

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

### Bug Fixes

* **export:** mark extension as reproducible ([8d61b2e0](https://git.gitlab.arm.com/bazel/toolchain_utils/commit/8d61b2e0a76c64393fc5c43428c653f1f4fa5e5b))

Prevents adding repositories into the lockfile.

# [1.0.0-beta.10](https://git.gitlab.arm.com/bazel/toolchain_utils/compare/v1.0.0-beta.9...v1.0.0-beta.10) (2024-05-22)

### Bug Fixes

* **info:** make var matches info ([f82eb108](https://git.gitlab.arm.com/bazel/toolchain_utils/commit/f82eb1082dc5858231ab937d4cec4698678e5f6e))

This commit updates the make variable
exported by `toolchain_info` to match the
`ToolchainInfo` provider.

# [1.0.0-beta.9](https://git.gitlab.arm.com/bazel/toolchain_utils/compare/v1.0.0-beta.8...v1.0.0-beta.9) (2024-05-03)

### Features

* add `toolchain_info` rule ([11ea2416](https://git.gitlab.arm.com/bazel/toolchain_utils/commit/11ea241647f87759bebd2c5ce7a7b0bdba55953a))

### BREAKING CHANGES

* The `toolchain_symlink_target` no longer exports
`ToolchainInfo`/`TemplateVariableInfo`.

The `toolchain_info` can provide those providers. The `toolchain_symlink_target`
is purely for creating a symlink to a previous target. This still enables
changing the basename for multi-call binaries.

To gain the old functionality, if `basename` attribute is not being used,
`toolchain_symlink_target` can be switched directly for `toolchain_info`. If
`basename` is being used, an extra `toolchain_info` rule will need to be created
to wrap the `toolchain_symlink_target` rule.

BREAKING CHANGE: The `toolchain_symlink_target` no longer exports
`ToolchainInfo`/`TemplateVariableInfo`.

The `toolchain_info` can provide those providers. The `toolchain_symlink_target`
is purely for creating a symlink to a previous target. This still enables
changing the basename for multi-call binaries.

To gain the old functionality, if `basename` attribute is not being used,
`toolchain_symlink_target` can be switched directly for `toolchain_info`. If
`basename` is being used, an extra `toolchain_info` rule will need to be created
to wrap the `toolchain_symlink_target` rule.

# [1.0.0-beta.8](https://git.gitlab.arm.com/bazel/toolchain_utils/compare/v1.0.0-beta.7...v1.0.0-beta.8) (2024-05-03)

### Bug Fixes

* **symlink/target:** add `run` property on `ToolchainInfo` provider ([0f18fef6](https://git.gitlab.arm.com/bazel/toolchain_utils/commit/0f18fef6742b133d2da0d0c920bc0fda30e14214))

### BREAKING CHANGES

* **symlink/target:** the `files_to_run` property has been removed from the `ToolchainInfo` provider. Use `info.default.files_to_run` instead.

A new `info.run` has been added that is `info.default.files_to_run` or `info.default.executable`.
This is a convenience property that can be passed to `ctx.actions.run#execute`.

BREAKING CHANGE: the `files_to_run` property has been removed from the `ToolchainInfo` provider. Use `info.default.files_to_run` instead.

A new `info.run` has been added that is `info.default.files_to_run` or `info.default.executable`.
This is a convenience property that can be passed to `ctx.actions.run#execute`.

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

### Bug Fixes

* **symlink/target:** add `files_to_run` property on `ToolchainInfo` provider ([2966744e](https://git.gitlab.arm.com/bazel/toolchain_utils/commit/2966744e1328bef9143dbb5c9c1d32fc756e0219))
* **symlink/target:** add target to runfiles ([4ec23317](https://git.gitlab.arm.com/bazel/toolchain_utils/commit/4ec23317cba14be99c3eec807e9b3873fc5636b0))
* **symlink/target:** merge all data runfiles ([753b43a4](https://git.gitlab.arm.com/bazel/toolchain_utils/commit/753b43a44ff14e768dd98f9fd9234d4f30eb3d0d))
* **toolchain/test:** break `diff` loop correctly ([d57cc719](https://git.gitlab.arm.com/bazel/toolchain_utils/commit/d57cc71913ae936d26ed4a385ad3eb24bde6e8d9))

### BREAKING CHANGES

* **symlink/target:** `toolchain_symlink_path` no longer provides `ToolchainInfo`/`TemplateVariableInfo`.

It is required to use `toolchain_symlink_target` to the `toolchain_symlink_path`.

This is due to `toolchain_symlink_target` needing to export the `DefaultInfo.file_to_run` from the
symlinked target. That is not possible with a filesystem path.

This should not affect most users as `toolchain_symlink_path` is mainly used in `toolchain_local_which`.

If `toolchain_symlink_path` is being used, then to gain the previous functionality, create a
`toolchain_symlink_target` to the `toolchain_symlink_path` label.

BREAKING CHANGE: `toolchain_symlink_path` no longer provides `ToolchainInfo`/`TemplateVariableInfo`.

It is required to use `toolchain_symlink_target` to the `toolchain_symlink_path`.

This is due to `toolchain_symlink_target` needing to export the `DefaultInfo.file_to_run` from the
symlinked target. That is not possible with a filesystem path.

This should not affect most users as `toolchain_symlink_path` is mainly used in `toolchain_local_which`.

If `toolchain_symlink_path` is being used, then to gain the previous functionality, create a
`toolchain_symlink_target` to the `toolchain_symlink_path` label.

Prevents a circular dependency between `toolchain_utils`, `ape` and `rules_diff`
which negatively impacts developer experience when changing
`toolchain_utils`.

Brings Apple Silicon and remote execution support.

# [1.0.0-beta.6](https://git.gitlab.arm.com/bazel/toolchain_utils/compare/v1.0.0-beta.5...v1.0.0-beta.6) (2024-04-24)

### Bug Fixes

* **symlink/target:** accept extensions without period `.` ([ab12aa8c](https://git.gitlab.arm.com/bazel/toolchain_utils/commit/ab12aa8c9d22d80d949b3c8e213a5a4b4cc9e121))

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

### Features

* support detecting triplet on MinGW ([ff280ae0](https://git.gitlab.arm.com/bazel/toolchain_utils/commit/ff280ae0b1aed1bfca9b667b07ddbb657e98cfc6))

# [1.0.0-beta.4](https://git.gitlab.arm.com/bazel/toolchain_utils/compare/v1.0.0-beta.3...v1.0.0-beta.4) (2024-03-25)

### Bug Fixes

* **export.symlink:** support multiple identical exports ([07a9c2c8](https://git.gitlab.arm.com/bazel/toolchain_utils/commit/07a9c2c832997967deaed6a8257789a03bf3450b))

A module can be in the module graph multiple times.

Each time the module is evaluated, a `export.symlink` tag will be created.

We can walk the graph to make sure that all exports are identical and
export once.