## [1.0.8](https://git.gitlab.arm.com/bazel/pre-commit/compare/v1.0.7...v1.0.8) (2025-07-24)

### Bug Fixes

* change config yaml format ([2ac46306](https://git.gitlab.arm.com/bazel/pre-commit/commit/2ac463068c55bbdb4ae890dd58d27d3f0f599f95))
* **pre-commit:** support RUNFILES_MANIFEST_FILE ([e67c1576](https://git.gitlab.arm.com/bazel/pre-commit/commit/e67c1576e73a7e0d61d3fd54bbc962d90291cdde))

We can't load a runfiles folder when `RUNFILES_MANIFEST_FILE` is set, as
it won't be listed explicitly there.

## [1.0.7](https://git.gitlab.arm.com/bazel/pre-commit/compare/v1.0.6...v1.0.7) (2025-06-03)

### Bug Fixes

* correct temporary output move when using YAML `SafeDumper` ([ba670a07](https://git.gitlab.arm.com/bazel/pre-commit/commit/ba670a0709a4160595e9d496081692aac0927194))
* pip cross platform build ([b4fecbec](https://git.gitlab.arm.com/bazel/pre-commit/commit/b4fecbec073a75779638e089650a03ed074ecc15))
* redundant print ([c79de8d8](https://git.gitlab.arm.com/bazel/pre-commit/commit/c79de8d8edfed62afc9437d8bf6363495a94501c))

We can use the `TemporaryRedirectFile` class directly as it implements the `SupportsWriteFlush[str]` protocol.

When a `CSafeDumper` is not available, we fallback to `SafeDumper`.

This correctly invokes the `__del__` function in the order that the garbage collector runs.

It results in the following error:

```
Exception ignored in: <function Closer.__del__ at 0x7f9547c3b420>
Traceback (most recent call last):
  File ".../pre-commit/config/cli.runfiles/_main/pre-commit/config/cli.py", line 175, in __del__
    self.close()
  File ".../pre-commit/config/cli.runfiles/_main/pre-commit/config/cli.py", line 170, in close
    self.__file.flush()
  File ".../python3.13/tempfile.py", line 499, in func_wrapper
    return func(*args, **kwargs)
ValueError: I/O operation on closed file.
```

This occurs because the `NamedTemporaryFile.__del__` runs before the `Closer.__del__`.

The `NamedTemporaryFile.__del__` closes then, then deletes the file. Setting `delete=False` will not help.

We move the `NamedTemporaryFile` into the `Closer` (renamed to `TemporaryRedirectFile`) to correct the closing order.

All `pip.parse` extensions from `rules_python` should
have `experimental_index_url` attribute for correct
platform dependent packages checkout.

See: https://github.com/bazel-contrib/rules_python/blob/main/docs/pypi-dependencies.md#bazel-downloader-and-multi-platform-wheel-hub-repository

Remove redundant `print()` call to `stdout`.

## [1.0.6](https://git.gitlab.arm.com/bazel/pre-commit/compare/v1.0.5...v1.0.6) (2025-05-12)

### Bug Fixes

* multi-platform wheel repo fetch ([835a7252](https://git.gitlab.arm.com/bazel/pre-commit/commit/835a725261b7ae030616c541df3b42ae3a469582))

Add `experimental_index_url` to fetch available wheel repos
for needed platforms.

This does not mean that rules_python is fetching the wheels eagerly,
but it rather means that it is calling the PyPI server to get the
Simple API response to get the list of all available source and
wheel distributions.

## [1.0.5](https://git.gitlab.arm.com/bazel/pre-commit/compare/v1.0.4...v1.0.5) (2025-05-07)

### Bug Fixes

* make config list sorting deterministic ([d90837cf](https://git.gitlab.arm.com/bazel/pre-commit/commit/d90837cfe393493e7cac696b68f8d1d57cc7c252))
* pip spoke whl repository platform ([6daa9df9](https://git.gitlab.arm.com/bazel/pre-commit/commit/6daa9df9f60f9d7d1780421be21a5d12c3d5117f))

Having:
```py
pip.parse(
    hub_name = "pre-commit-hook-{}".format(version),
    python_version = version,
    requirements_lock = "//pre-commit/hook/requirements:lock.txt",
),
```
and using `requirements_lock` attribute will create pip spoke whl
repositories just for the host platform.

This can have potential issues when the repository is platform
dependent and the host platform is different of execution platform
(common case for RBE build).

The change sets pip requirements for different platforms separately.

Specifying platforms as:
  - `"linux_*"`
  - `"osx_*"`
  - `"windows_*"`
allows the pip to create repositories for different platforms and
picks up correct one for the execution platform.

## [1.0.4](https://git.gitlab.arm.com/bazel/pre-commit/compare/v1.0.3...v1.0.4) (2025-03-10)

### Bug Fixes

* use `Label` for hardcoded target in macro ([30841a93](https://git.gitlab.arm.com/bazel/pre-commit/commit/30841a932126aeaad88c9d827a677f64fff397e2))

Leftover from aeea1465.

## [1.0.3](https://git.gitlab.arm.com/bazel/pre-commit/compare/v1.0.2...v1.0.3) (2025-03-10)

### Bug Fixes

* remove need to register Python 3.13 toolchain ([c0cd53eb](https://git.gitlab.arm.com/bazel/pre-commit/commit/c0cd53eb85d9badba7b73b789bb4953862021a21))

Users shouldn't need to register an additional toolchain if they're
already using a different version of Python.

## [1.0.2](https://git.gitlab.arm.com/bazel/pre-commit/compare/v1.0.1...v1.0.2) (2025-03-05)

### Bug Fixes

* make Windows non-support explicit ([aeea1465](https://git.gitlab.arm.com/bazel/pre-commit/commit/aeea1465a063d1e895856d02152ff9f2e9499be5)), closes [#1](https://git.gitlab.arm.com/bazel/pre-commit/issues/1)

Setting the compatiblilty for the configuration generation rule ensures that we do not support Windows.

There is no technical barrier here, it just needs thorough testing.

Currently, the hermetic bootstrap script for `rules_python` is failing on Windows.

See #1

## [1.0.1](https://git.gitlab.arm.com/bazel/pre-commit/compare/v1.0.0...v1.0.1) (2025-03-05)

### Bug Fixes

* **pre-commit:** validate that a runfile is resolved ([b4b8edba](https://git.gitlab.arm.com/bazel/pre-commit/commit/b4b8edba478799231fae032ba29e4a2c88fba10d))
* strip trailing Bazel module separator from workspace name ([b2457f44](https://git.gitlab.arm.com/bazel/pre-commit/commit/b2457f4410ea941b9bc3119121beb58d3879c2f9))