## [1.0.2](v1.0.1...v1.0.2) (2024-01-22)

### Bug Fixes

* publish package to GitLab registry ([87cdda91](87cdda91))

The timeout is measured in milliseconds. Whoops!

reverts: 83a59329

`ava@6` does not exit worker threads/processes.

We have leaky tests. Downgrading whilst we figure out what they are.

https://github.com/avajs/ava/releases/tag/v6.0.0

## [1.0.1](v1.0.0...v1.0.1) (2024-01-22)

### Bug Fixes

* **package:** allow `dockerode^4` ([65dc5cfe](65dc5cfe))
* **release:** upload package tarball ([79e2688e](79e2688e))

Currently failing due to the wrapped method not being found.

Not needed for all the tests to pass.

# 1.0.0 (2023-08-03)

### Bug Fixes

* allow major version 3 or 4 of `semantic-release/error` ([f0faec8b](f0faec8b))
* fine-tune logging output ([9563f013](9563f013))
* **package:** add `./` prefix to exports ([4249398f](4249398f))

### Features

* allow `tag` in plugin config for default tag replacement ([6f0b6e2c](6f0b6e2c))
* plugin at `@semantic-release/dockerode-tag` ([53744514](53744514))

Moves everything into `.gitlab-ci.yml`

Requires bumping the plugins as they depend on the breaking change to
ECMAscript modules:

- `@semantic-release/commit-analyzer@^10`
- `@semantic-release/gitlab@^12`
- `@semantic-release/release-notes-generator@^11`

We already import it as a ECMAscript module so the breaking
change does not affect us.

It is available in NodeJS 15 which is below our lowest
version of NodeJS 18.

We do not have a package registry enabled on our GitLab at this time.

Prevent an attempt to publish the package.

`semantic-release` 20 will be ESM first and only work on
NodeJS 18+. Prepare for that now by dropping old versions
in the CI.

We do not use anything from the breaking API change.