Resolve "Semrel Imga 3.10.0"

Closes #41

See merge request to-be-continuous/semantic-release!56

# [3.10.0](https://gitlab.com/to-be-continuous/semantic-release/compare/3.9.1...3.10.0) (2024-05-20)

### Features

* use slim image by default (shortens job execution time)  ([8dbd5da4](https://gitlab.com/to-be-continuous/semantic-release/commit/8dbd5da4b489492523e9c678fa1c2b19dcd65283))

Use slim image

See merge request to-be-continuous/semantic-release!55

Slim images are much smaller, speeding-up the job execution.

## [3.9.1](https://gitlab.com/to-be-continuous/semantic-release/compare/3.9.0...3.9.1) (2024-05-18)

### Bug Fixes

* semantic-release don't run on prod_ref ([49217b4d](https://gitlab.com/to-be-continuous/semantic-release/commit/49217b4dfcfe2cb6f5bea72cce10cb2af2a95d59))

Resolve "version `3.9.0` doesn't behave like previous ones with default config"

Closes #40

See merge request to-be-continuous/semantic-release!54

# [3.9.0](https://gitlab.com/to-be-continuous/semantic-release/compare/3.8.3...3.9.0) (2024-05-10)

### Features

* add SEMREL_REF to run semantic-release on a wider number of branches alongside info-on 'semrel' to use this variable ([74288afb](https://gitlab.com/to-be-continuous/semantic-release/commit/74288afbe3fb22ec8c973b228755243b012f998a))

feat: add SEMREL_REF to run semantic-release on a wider number of branches...

See merge request to-be-continuous/semantic-release!53

feat: add SEMREL_REF to run semantic-release on a wider number of branches alongside info-on 'semrel' to use this variable

Signed-off-by: Kilian PAQUIER <kilian@kilianpaquier.com>

## [3.8.3](https://gitlab.com/to-be-continuous/semantic-release/compare/3.8.2...3.8.3) (2024-05-05)

### Bug Fixes

* **workflow:** disable MR pipeline from prod & integ branches ([0bdec1c6](https://gitlab.com/to-be-continuous/semantic-release/commit/0bdec1c625b01ad7b96629f5d448583fab9a1969))

Today creating a backmerge MR from prod or integ branch to any other branch triggers a pipeline
even though no change has been pushed.
Ultimately those pipelines might (re)trigger integration or production environment deployment and/or packages publication.
That might have unexpected consequences.
This change simply disables MR pipeline from prod & integ branches, enforcing branch pipelines only (i.e. when a true commit is pushed).

## [3.8.2](https://gitlab.com/to-be-continuous/semantic-release/compare/3.8.1...3.8.2) (2024-04-03)

### Bug Fixes

* **vault:** use vault-secrets-provider's "latest" image tag ([7b3902db](https://gitlab.com/to-be-continuous/semantic-release/commit/7b3902db57fec34c4a46b500c19d6ba90d6bff42))

## [3.8.1](https://gitlab.com/to-be-continuous/semantic-release/compare/3.8.0...3.8.1) (2024-04-02)

### Bug Fixes

* allow semantic-release-info to be generated on the commit branch ([7876e3e7](https://gitlab.com/to-be-continuous/semantic-release/commit/7876e3e7dab07671c87a65c325f1a86ed71cdbf5))

Merge branch '35-semantic-release-info-job-doesn-t-work-on-protected-branches-other-than-the-semantic-release' into 'master'

Resolve "semantic-release-info job doesn't work on protected branches other than the semantic-release default"

Closes #35

See merge request to-be-continuous/semantic-release!50

chore(deps): update dependency to-be-continuous/bash to v3.4

See merge request to-be-continuous/semantic-release!48

# [3.8.0](https://gitlab.com/to-be-continuous/semantic-release/compare/3.7.1...3.8.0) (2024-1-30)

### Bug Fixes

* <SEMREL_RELEASE_DISABLED/release-disabled> type ([02b6dd4b](https://gitlab.com/to-be-continuous/semantic-release/commit/02b6dd4b654e32effc5ea9f3f8f774f2a82b38a9))
* dry run option ([6b05408e](https://gitlab.com/to-be-continuous/semantic-release/commit/6b05408e85f635f350a0d2651ea0cff1dadd91ba))
* sanitize variable substitution pattern ([3ac15e7c](https://gitlab.com/to-be-continuous/semantic-release/commit/3ac15e7c508a255a04e2f3df5f37eeab61e8340e))

### Features

* migrate to CI/CD component ([4ff79966](https://gitlab.com/to-be-continuous/semantic-release/commit/4ff7996643f34a6dd3e590b3c1f8cb6581dab042))

replace '${foo+repl}' pattern with '${foo:+repl}' (latest supports $foo being defined but empty)

feat: migrate to CI/CD component

See merge request to-be-continuous/semantic-release!47

 requires GitLab 16.6 or later

## [3.7.1](https://gitlab.com/to-be-continuous/semantic-release/compare/3.7.0...3.7.1) (2024-1-16)

### Bug Fixes

* **gpg:** create base folder if not present ([d69fae20](https://gitlab.com/to-be-continuous/semantic-release/commit/d69fae20f297d6e06333e8faac2c236fb824d37f)), closes [#32](https://gitlab.com/to-be-continuous/semantic-release/issues/32)

fix(gpg): create base folder if not present

Closes #32

See merge request to-be-continuous/semantic-release!46

On newest node docker images, `${HOME}/.gnupg` folder is not present and
the script fails.
Be sure to create the folder and needed files in it before importing
key.

closes #32

Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>

chore(deps): update dependency to-be-continuous/bash to v3.3

See merge request to-be-continuous/semantic-release!45

# [3.7.0](https://gitlab.com/to-be-continuous/semantic-release/compare/3.6.0...3.7.0) (2023-12-8)

### Features

* use centralized service images (gitlab.com) ([6b117cc0](https://gitlab.com/to-be-continuous/semantic-release/commit/6b117cc0cca69deed7d8c62429482555673c8181))