Publish new release

See merge request !44

Prepare a new release

See merge request !43

feat(semantic-release): switch to `conventionalcommits` changelog

Closes #7

See merge request !42

The `conventional-changelog-conventionalcommits` permits to easily
configure which commit types are rendered or not in the changelog and
releases.

* Dockerfile.semantic-release-gitlab: the module must be installed.

* release.config.js: switch to `conventionalcommits` and configure the
  commit `types`.

# [1.6.0](https://gitlab.mim-libre.fr/EOLE/infra/ci-tools/compare/release/1.5.0...release/1.6.0) (2022-03-15)

### Features

* **git:** new `.git:merge-to` job template to merge a reference ([f8501fc7](f8501fc7))

Publish new release

See merge request !41

Prepare new release

See merge request !40

ci(release): generate releases using the new template job

See merge request !38

And use the shorter `release.config.js` file with recent
`semantic-release` fixes.

feat(git): new `.git:merge-to` job template to merge a reference

Closes #6

See merge request !37

By default, the source of the merge is `${CI_COMMIT_TAG}` and the
target must be defined by the `.gitlab-ci.yml` job using this
template.

* docs/GETTING-STARTED.md: new section to document `.git:merge-to`
  template job.

* templates/Git.yaml: new `.git:merge-to` template job to merge a
  reference into a target branch.

refactor(templates): we factorize the job templates per topic

Closes #4

See merge request !36

Building a docker image is now done by `.docker:image:build` job
template.

Tagging a docker image is now done by `.docker:image:tag` job
template.

We keep the previous job templates for backward compatibility.

* templates/Docker.yaml: new `.docker:image:build` and
  `.docker:image:tag` job templates.

Using `semantic-release` require the users to include
`templates/Semantic-release.yaml` and `extends` the `.semantic-release:*`
job templates.

We keep `templates/Release/Semantic-release.yaml` for backward
compatibility.

* templates/Semantic-release.yaml: new `semantic-release` related job
  templates

* templates/Lint/Commitlint.yaml: define `semantic-release` with the
  `.semantic-release:stable` job template for backward compatibility.

Using `commitlint` require the users to include `templates/Git.yaml`
and `extends` the `.git:commitlint` job template.

We keep `templates/Lint/Commitlint.yaml` for backward compatibility.

* templates/Git.yaml: new git related job templates

* templates/Lint/Commitlint.yaml: define `commitlint` with the
  `.git:commitlint` job template for backward compatibility.

* .commitlintrc.yaml: move from JS to YAML.

Instead of having files with executable jobs, we define only hidden
template jobs that users must `instanciate` in their own
`.gitlab-ci.yml`.

# [1.5.0](https://gitlab.mim-libre.fr/EOLE/infra/ci-tools/compare/release/1.4.0...release/1.5.0) (2022-02-16)

### Documentation

* **getting-started:** generate prerelease version for `testing` ([733fb661](EOLE/infra/ci-tools@733fb661))

### Features

* **commitlint:** update `commitlint` to version 16 ([d003342a](EOLE/infra/ci-tools@d003342a))
* **docker:** tag docker image of contributor branches ([1ddb17e4](EOLE/infra/ci-tools@1ddb17e4))
* **semantic-release:** new job templates for prerelease ([879854fe](EOLE/infra/ci-tools@879854fe))
* **semantic-release:** update to version `19` ([92aceec9](EOLE/infra/ci-tools@92aceec9))

Publish the new release

See merge request !35

Prepare new release

See merge request !34

feat(docker): tag docker image of contributor branches

See merge request !33

feat(semantic-release): update to version `19`

See merge request !32

feat(commitlint): update `commitlint` to version 16

See merge request !31

feat(semantic-release): new job templates for prerelease

See merge request !30

The docker image build for `$TESTING_BRANCH` is done after
`semantic-release` version generation.

By default, a `semantic-release` job is created for `$STABLE_BRANCH`
and you can create jobs for `$TESTING_BRANCH` and `$DEV_BRANCH` by
extending the `.semantic-release:testing` and `.semantic-release:dev`
template jobs.

# [1.4.0](https://gitlab.mim-libre.fr/EOLE/infra/ci-tools/compare/release/1.3.0...release/1.4.0) (2022-01-24)

### Features

* **rules:** support prerelease tags for `semantic-release` ([0ec996ac](EOLE/infra/ci-tools@0ec996ac))
* **semantic-release/config:** easier declaration of branches ([c7acd281](EOLE/infra/ci-tools@c7acd281))
* **semantic-release:** new rules for prerelease ([b2752bd9](EOLE/infra/ci-tools@b2752bd9))

Publish new release

See merge request EOLE/infra/ci-tools!29

Prepare a new release

See merge request EOLE/infra/ci-tools!28

feat(semantic-release): support prerelease for `testing` and `dev` branches

See merge request EOLE/infra/ci-tools!27

New `.on-testing-with-semantic-release-config` and
`.on-dev-with-semantic-release-config` rules.

Create a new `.semantic-release:stable` template job and use it for
the default `semantic-release` job.

* release.config.js: declare 3 variables for `stable`, `testing` and
  `dev` branches.
  By default, `testingBranch` and `devBranch` are undefined and users
  only need to declare them to enable prerelease for them.

The previous `.on-release-tag` match everything starting with
`release/` and so prerelease tags like `release/X.Y.Z-testing` or
`release/X.Y.Z-dev`.

When doing prerelease, we want to avoid updating stable tags, we
restrict the match for release tags and add specific rules to match
`testing` and `dev` tags.

# [1.3.0](https://gitlab.mim-libre.fr/EOLE/infra/ci-tools/compare/release/1.2.1...release/1.3.0) (2022-01-11)

### Bug Fixes

* **semantic-release:** the branch must be `stable` ([4b9152dc](EOLE/infra/ci-tools@4b9152dc))

### Code Refactoring

* **commitlint:** the upstream extra repository is useless ([cdff4abd](EOLE/infra/ci-tools@cdff4abd))

### Documentation

* **commitlint:** describe usage of the commitlint job ([8b3749f0](EOLE/infra/ci-tools@8b3749f0))
* **getting-started:** quick setup and detailed explanations ([007aa219](EOLE/infra/ci-tools@007aa219))
* **readme:** demonstrate a possible release cycle ([8d02a0cf](EOLE/infra/ci-tools@8d02a0cf))

### Features

* **commitlint:** users can configure image with `$COMMITLINT_IMAGE` ([bc7f19c3](EOLE/infra/ci-tools@bc7f19c3))
* **commitlint:** users can configure the base branch ([612dc3ea](EOLE/infra/ci-tools@612dc3ea))
* **docker:** .build-docker-image must accept kaniko arguments ([bd5c77ea](EOLE/infra/ci-tools@bd5c77ea))
* **semantic-release:** don't build changelog on prerelease branches ([5a02f5d2](EOLE/infra/ci-tools@5a02f5d2))
* **semantic-release:** manage python projects releases ([9794bcb0](EOLE/infra/ci-tools@9794bcb0))

### Styles

* **js:** js configuration files do not pass eslint ([5874dca3](EOLE/infra/ci-tools@5874dca3))

fix(semantic-release): the branch must be `stable`

See merge request EOLE/infra/ci-tools!26

When doing backport of evolutions from other project, the `branches`
parameter was reset to `master`.

Publish a new release

See merge request EOLE/infra/ci-tools!25