Ensure bazelisk is installed before running any tests or development scripts.
The Bazel executable version can be specified by either setting the DEVELOPMENT_BAZEL_VERSION environment variable when running the test script, or by placing a .bazelversion file at the workspace root.
To run unit tests, execute development/cli/execute_unit_tests.bash. This script runs bazelisk test and bazelisk build commands.
Note that some test targets are marked with tags = ["manual"] and are intended to individually verify that bazel build fails as expected.
To run the integration tests, execute development/cli/execute_integration_tests.bash.
This script executes bazelisk test in each integration test directory.
If one or more directories are passed as arguments, only those directories are tested.
If no arguments are provided, all directories under tests/integration are tested.
To validate examples, run development/cli/validate_example.bash. This script runs bazelisk test inside the examples directory.
For formatting and linting, execute development/cli/style_check.bash.
This script checks for style consistency across the codebase.
Only an admin user can release a new version. To initiate a release, the admin should push a tag in the format X.Y.Z (e.g., 1.0.0). This will trigger a CI job that:
- Builds and uploads a tarball
- Creates a GitHub release
- Opens a pull request in the Bazel Central Registry (BCR)
After the BCR PR is approved and merged, the rules_build_error module becomes available as a Bazel module.