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

Alex Tercete authored Feb 28, 2025 and Matthew Clarkson committed Feb 28, 2025

When integrated with `@pre-commit-hooks`, the YAML config was being
generated with `@pre-commit-hooks~` as the workspace name, which caused
errors when trying to run the hooks.

In Bazel 8 the separator is `+`.

# 1.0.0 (2025-02-27)

### Bug Fixes

* remove restriction to pass `srcs`/`deps` to `pre_commit_config` ([ed52c063](https://git.gitlab.arm.com/bazel/pre-commit/commit/ed52c063cdf23ee7e13533739016345116c4855c))
* run config update on module lockfile changing ([39636c4a](https://git.gitlab.arm.com/bazel/pre-commit/commit/39636c4a552386f8f68aec625edf310dcc50a652))

### Features

* implement `pre_commit` macro ([88fb9648](https://git.gitlab.arm.com/bazel/pre-commit/commit/88fb9648067d6e76dbc8d35a4e537ad5b9d34e07))

Easy for the user. Does not describe the dependnecy relationship chain.

#YOLO

Prevents regenerating the lockfile.

It is valid to pass zero hooks and generate a blank configuration.

`semantic-release` sets it for us.

Will be set by `semantic-release`.

This is a **huge** patch that implements the functionality to use Bazel run targets as `pre-commit` hooks.

It provides the following rules:

- `pre_commit`: a macro that bundles the below rules
- `pre_commit_hook`: a macro to select a specific Bazel command rule such as `pre_commit_hook_run`
- `pre_commit_hook_run`: creates a `pre-commit` hook description that executes `bazel run` for the provided target
- `pre_commit_hooks`: bundles multiple `pre_commit_hook` rules together for easy usage
- `pre_commit_config`: accepts `pre_commit_hook{,s}` and generates a `.pre-commit-config.yaml` file
- `pre_commit_install`: installs a provided `.pre-commit-config.yaml` file into `.git/hooks`
- `pre_commit_run`: performs `pre-commit run` against the provided `.pre-commit-config.yaml` file
- `pre_commit_stage`: describes a `pre-commit` hook stage to be used with `pre_commit_hook`
- `pre_commit_tag`: describes a `pre-commit` hook file type tag to be used with `pre_commit_hook`

It has the following providers:

- `PreCommitConfigInfo`: a generated configuration file
- `PreCommitHookJSONInfo`: a provider that can be serialized to JSON for ingestion into `pre_commit_config`
- `PreCommitHookInfo`: a generated JSON file that `pre_commit_config` can parse and generate a configuration from
- `PreCommitHooksInfo`: contains a `depset` of `PreCommitHookInfo` providers
- `PreCommitTagInfo`: contains a `identify` file kind tag
- `PreCommitStageInfo`: contains a `pre-commit` hook stage

It has the following public labels:

- `@pre-commit`: a monkey patched `pre-commit` to ensure it works with Bazel effectively and provides a hermetic `git` and `bazel` implementation for running the hooks
- `@pre-commit//pre-commit:pkg`: a `py_library` that provdes the `pre_commit` Python module. Uses universal lockfiles and Python version `select` to provide the correct module to downstream users.
- `@pre-commit//pre-commit/git`: a `label_flag` for changing the hermetic `git` implementation used
- `@pre-commit//pre-commit/bazel`: a `label_flag` for changing the hermetic `bazel` implementation used
- `@pre-commit//pre-commit/stage:*`: stages to be used with `pre_commit_hook#stages`
- `@pre-commit//pre-commit/tag:*`: tags to be used with `pre_commit_hook#types{,_or}`