# [3.11.0](https://git.code.tecnalia.com/smartdatalab/public/ci-cd-components/semantic-release/compare/3.10.3...3.11.0) (2024-07-02)

### Features

* add support for configuring a commit specification (e.g. "conventional commits") ([c4519fdb](https://git.code.tecnalia.com/smartdatalab/public/ci-cd-components/semantic-release/commit/c4519fdb1100437dced3ba2bf93c8c069545f303))

# Conflicts:
#	CHANGELOG.md
#	kicker.json

feat: add support for defining a commit specification, e.g., conventional commits

Closes #39

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

## [3.10.3](https://gitlab.com/to-be-continuous/semantic-release/compare/3.10.2...3.10.3) (2024-06-02)

### Bug Fixes

* npm cache and add yq cache ([1fc7b1ac](https://gitlab.com/to-be-continuous/semantic-release/commit/1fc7b1ac6460c72e53b386b456997a9aa84ece35))

fix: npm cache and add yq cache

Closes #42

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

## [3.10.2](https://gitlab.com/to-be-continuous/semantic-release/compare/3.10.1...3.10.2) (2024-06-02)

### Bug Fixes

* provide a node-based implementation to retrieve url secrets ([f4e5a225](https://gitlab.com/to-be-continuous/semantic-release/commit/f4e5a225aa9816db907dc432cd842d86918ae838)), closes [#43](https://gitlab.com/to-be-continuous/semantic-release/issues/43)

Fixes #43

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

### Bug Fixes

* install gpg ([9533525a](https://gitlab.com/to-be-continuous/semantic-release/commit/9533525aa8143bf93e84e41aaf4aed82ab01db15))

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://git.code.tecnalia.com/smartdatalab/public/ci-cd-components/semantic-release/compare/3.8.3...3.9.0) (2024-05-13)

### Features

* add SEMREL_REF to run semantic-release on a wider number of branches alongside info-on 'semrel' to use this variable ([74288afb](https://git.code.tecnalia.com/smartdatalab/public/ci-cd-components/semantic-release/commit/74288afbe3fb22ec8c973b228755243b012f998a))

# [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).