# 1.0.0-alpha.1 (2023-11-15)

### Code Refactoring

* switch to `.bazelisk-fragment` ([7afa43ba](https://git.gitlab.arm.com/ci/component/bazelisk/commit/7afa43badf14d986666b8fb6c70ef0e3773b48f7))

### Features

* image build and CI component ([fb002de9](https://git.gitlab.arm.com/ci/component/bazelisk/commit/fb002de994aa01efec0543432529241bacd71420))

### BREAKING CHANGES

* `.bazelisk-script` is now `.bazelisk-fragment`

Update any `!reference[.bazelisk-script, ...]` to `!reference[.bazelisk-fragment, ...]`

_Eventually_, we want to be able to drive `semantic-release` from Bazel.

However, that requires hermetic resolution of `git` and `ssh` which is a
challenge that we do not have time for at this time.

`.bazelisk-script` implies everything must be a script reference.

We may want to include other references in the future.

Fragment is better nomenclature here.

BREAKING CHANGE: `.bazelisk-script` is now `.bazelisk-fragment`

Update any `!reference[.bazelisk-script, ...]` to `!reference[.bazelisk-fragment, ...]`

Builds a `bazelisk` image for multiple architectures using `rules_oci`.

Provides a `template.yml` GitLab CI component.