Resolve "URLs generated for changelog and Releases are invalid"

Closes #21

See merge request !67

This is due to `conventional-changelog` using github URLs by default.

* .releaserc.js: add configure option to format URLs for gitlab.

Resolve "Python: remove the useless `semantic-release-pypi`"

Closes #23

See merge request !68

The `semantic-release-pypi` only works with `setup.py` / `setup.cfg`.

BREAKING CHANGE: `semantic-release-pypi` is not longer included as a plugin

* Dockerfile.semantic-release-gitlab: remove `semantic-release-pypi`
  plugin and its dependencies.

The `semantic-release-pypi` only works with `setup.py` / `setup.cfg`.

BREAKING CHANGE: use `@semantic-release/exec` instead of `semantic-release-pypi`

* .releaserc.js: define an example using `@semantic-release/exec` to
  execute a `sed` command.

## [1.12.0](https://gitlab.mim-libre.fr/EOLE/infra/ci-tools/compare/release/1.11.1...release/1.12.0) (2022-07-05)

### Features

* **maven:** copy package to remote repository with `.maven:deploy` ([b72b0a82](b72b0a82))
* **maven:** ensure quality criteria are met with `.maven:verify` ([a46a2368](a46a2368))
* **maven:** validate the project with `.maven:validate` ([92d822d4](92d822d4))

### Bug Fixes

* **maven:** define `SRC_DIR` variable ([8d8a6af8](8d8a6af8))

Publish new release

See merge request !66

Prepare new release

See merge request !65

Resolve "Maven: source directory variable is not set"

Closes #19

See merge request !64

This variable should be defined in `.maven:base` or errors can occurs
at CI:

    POM file  specified with the -f/--file command line argument does not exist

Resolve "Add CI templates for Java Maven projects"

Closes #18

See merge request !63

USAGE
=====

include:
  - project: EOLE/Infra/ci-tools
    ref: stable
    file: /templates/Maven.yaml

stages:
  - release

maven deploy: {extends: '.maven:deploy'}

USAGE
=====

include:
  - project: EOLE/Infra/ci-tools
    ref: stable
    file: /templates/Maven.yaml

stages:
  - test

maven verify: {extends: '.maven:verify'}

.maven:validate
===============

Validate the project is correct and all necessary information is
available.

USAGE
=====

include:
  - project: EOLE/Infra/ci-tools
    ref: stable
    file: /templates/Maven.yaml

stages:
  - lint

maven validate: {extends: '.maven:validate'}

### [1.11.1](https://gitlab.mim-libre.fr/EOLE/infra/ci-tools/compare/release/1.11.0...release/1.11.1) (2022-06-28)

### Bug Fixes

* **.git:commitlint:** workaround loading project configuration ([fde1fc07](fde1fc07))

Resolve ".git:commitlint does not work for some typeScript project"

See merge request !62

When `commitlint` is executed in a repository containing a
`tsconfig.json` file, it try to load this configuration to use it.

This should be solved by the upstream issue

  https://github.com/conventional-changelog/commitlint/issues/3256

As a workaround, we execute `commitlint` from `/tmp` with the option
`--cwd ${CI_PROJECT_DIR}`.

* templates/Git.yaml (.git:commitlint): move to `/tmp` before
  execution.
  Pass the `--cwd` option to `commitlint`.

## [1.11.0](https://gitlab.mim-libre.fr/EOLE/infra/ci-tools/compare/release/1.10.0...release/1.11.0) (2022-06-23)

### Features

* **.git:commitlint:** skip no branch or semantic-release commit ([3a855ab0](3a855ab0))
* **helm:** build the helm package ([115a62a8](115a62a8))
* **helm:** publish the helm package ([98f3a6e4](98f3a6e4))
* **helm:** verify helm formatting with `.helm:lint` job template ([7e1ccbd3](7e1ccbd3))
* **semantic-release:** don't enforce configuration on job rules ([1a1a9cac](1a1a9cac))
* **semantic-release:** update version of Helm charts ([f776b127](f776b127))

### Bug Fixes

* **helm:** rename jobs to their used helm command ([7d6886c5](7d6886c5))

### Code Refactoring

* **semantic-release:** move rules in main configuration file ([2ba784d8](2ba784d8))

### Documentation

* **getting-started:** update `semantic-release` configuration steps ([b6d5bc56](b6d5bc56))

### Continuous Integration

* **build:** new docker image with required helm tools ([e6205685](e6205685))

Publish new release

See merge request !61

Prepare new release

See merge request !60

Resolve "Semantic-release commits blocs merging when pipeline is required"

Closes #15

See merge request !59

All branches should have at least on job to not block merge when
successful pipeline is required.

* templates/Rules.yaml (.on-branch): select any branch without
  excluding `semantic-release` commit.

Resolve "Helm: job template names must be consistent with command"

Closes #16

See merge request !58

This should avoid confusion by helm users:

- `.helm:build` became `.helm:package`
- `.helm:push` became `.helm:cm-push`

Merge branch '14-semantic-release-is-not-triggered-when-using-commonjs-extension-for-configuration-file' into 'dev'

Resolve "semantic-release is not triggered when using commonJS extension for configuration file"

Closes #14

See merge request !57

Resolve "Helm: provide CI templates to build and publish"

Closes #12

See merge request !56

* templates/Semantic-release.yaml: remove specific rules to test
  `semantic-release` configuration file existence.

USAGE
=====

include:
  - project: EOLE/Infra/ci-tools
    ref: master
    file: /templates/Helm.yaml

stages:
  - release

helm publish: {extends: '.helm:push'}

REQUIREMENTS
============

- a `release` stage must be present in your pipeline or it must be
  overriden by the extending job to feet your need.

- the `.not-on-stable` rules templates or it must be overriden by
  the extending job to feet your need

- `HELM_REPO` variable: URL of the helm ChartMuseum

- `HELM_REPO_USERNAME` variable : name of the user with write access
  to the ChartMuseum

- `HELM_REPO_PASSWORD` variable: password of `HELM_REPO_USERNAME`

OPTIONAL VARIABLES
==================

- `CHART_DIR`: directory of the helm chart, default to `.`

- `HELM_IMAGE`: name of the `helm` docker image to use

- `HELM_ARGS`: optional arguments to pass to `helm cm-push` command,
  empty by default

- `HELM_BUILD_DIR`: write package chart in this directory, default
  to `build`

USAGE
=====

include:
  - project: EOLE/Infra/ci-tools
    ref: master
    file: /templates/Helm.yaml

stages:
  - build

helm build: {extends: '.helm:build'}

REQUIREMENTS
============

- a `build` stage must be present in your pipeline or it must be
  overriden by the extending job to feet your need.

- the `.not-on-stable` rules templates or it must be overriden by
  the extending job to feet your need

OPTIONAL VARIABLES
==================

- `CHART_DIR`: directory of the helm chart, default to `.`

- `HELM_IMAGE`: name of the `helm` docker image to use

- `HELM_ARGS`: optional arguments to pass to `helm package` command,
   empty by default

- `HELM_BUILD_DIR`: write package chart in this directory, default
  to `build`

USAGE
=====

include:
  - project: EOLE/Infra/ci-tools
    ref: master
    file: /templates/Helm.yaml

stages:
  - lint

helm lint: {extends: '.helm:lint'}

REQUIREMENTS
============

- a `lint` stage must be present in your pipeline or it must be
  overriden by the extending job to feet your need.

- the `.not-on-stable` rules templates or it must be overriden by
  the extending job to feet your need

OPTIONAL VARIABLES
==================

- `CHART_DIR`: directory of the helm chart, default to `.`

- `HELM_IMAGE`: name of the `helm` docker image to use

- `HELM_ARGS`: optional arguments to pass to `helm lint` command,
  empty by default

We need the `helm` tool itself and the helm plugin
[`cm-push`](https://github.com/chartmuseum/helm-push) to upload to
harbor chartmuseum.

* Dockerfile.semantic-release-gitlab: add the forked
  [semantic-release-helm3](https://www.npmjs.com/package/semantic-release-helm3)
  plugin to support prerelease versions.

* .releaserc.js: add a commented configuration of the
  `semantic-release-helm3` plugin

Resolve "All semantic-release configuration should be in a single file"

Closes #13

See merge request !55