Girija Saint Ange authored Jan 24, 2024 and Pierre Smeyers committed Jan 27, 2024

⚠️ requires GitLab 16.6 or later

feat: migrate to CI/CD component

See merge request !47

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

# [3.8.0](3.7.1...3.8.0) (2024-1-30)

### Bug Fixes

* <SEMREL_RELEASE_DISABLED/release-disabled> type ([02b6dd4b](02b6dd4b))
* dry run option ([6b05408e](6b05408e))
* sanitize variable substitution pattern ([3ac15e7c](3ac15e7c))

### Features

* migrate to CI/CD component ([4ff79966](4ff79966))

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

See merge request !48

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 !50

## [3.8.1](3.8.0...3.8.1) (2024-04-02)

### Bug Fixes

* allow semantic-release-info to be generated on the commit branch ([7876e3e7](7876e3e7))

## [3.8.2](3.8.1...3.8.2) (2024-04-03)

### Bug Fixes

* **vault:** use vault-secrets-provider's "latest" image tag ([7b3902db](7b3902db))

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.3](3.8.2...3.8.3) (2024-05-05)

### Bug Fixes

* **workflow:** disable MR pipeline from prod & integ branches ([0bdec1c6](0bdec1c6))