# [1.5.0](1.4.1...1.5.0) (2025-01-29)

### Features

* disable tracking service by default ([0193166e](0193166e))

# Conflicts:
#	CHANGELOG.md

# [1.5.0](https://gitlab.com/to-be-continuous/renovate/compare/1.4.1...1.5.0) (2025-01-27)

### Features

* disable tracking service by default ([0193166e](https://gitlab.com/to-be-continuous/renovate/commit/0193166ef576061753d4cd9c80ac4cfd84c96109))

## [1.4.1](1.4.0...1.4.1) (2025-01-20)

### Bug Fixes

* renovate cannot upgrade overwritten TBC Docker images ([6a3794bd](6a3794bd))
* specifiy user agent to fix check links issue on mend.io ([2814754b](2814754b))

# Conflicts:
#	.gitlab-ci.yml
#	CHANGELOG.md
#	README.md
#	templates/gitlab-ci-renovate.yml

## [1.4.1](https://gitlab.com/to-be-continuous/renovate/compare/1.4.0...1.4.1) (2024-12-09)

### Bug Fixes

* renovate cannot upgrade overwritten TBC Docker images ([6a3794bd](https://gitlab.com/to-be-continuous/renovate/commit/6a3794bddfeed511543c3b8a912729302739f6ff))
* specifiy user agent to fix check links issue on mend.io ([2814754b](https://gitlab.com/to-be-continuous/renovate/commit/2814754b05915cafb1e171df4a212f65f855c2a7))

fix: specifiy user agent to fix check links issue on mend.io

Closes #6

See merge request to-be-continuous/renovate!15

Resolve "Renovate cannot upgrade overwritten TBC Docker images"

Closes #4

See merge request to-be-continuous/renovate!13

The default renovate configuration now detects overwritten TBC Docker image variables and tracks them for update

Signed-off-by: Clement Bois <clement.bois@orange.com>

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

See merge request to-be-continuous/renovate!11

# [1.4.0](https://gitlab.com/to-be-continuous/renovate/compare/1.3.0...1.4.0) (2024-08-30)

### Features

* standard TBC secrets decoding ([adf9450f](https://gitlab.com/to-be-continuous/renovate/commit/adf9450f9392d5ec7aced16a281e23346d190622))

# [1.3.0](https://git.code.tecnalia.com/smartdatalab/public/ci-cd-components/renovate/compare/1.2.2...1.3.0) (2024-08-29)

### Bug Fixes

* remove RENOVATE_PLATFORM as configurable param ([37f1acad](https://git.code.tecnalia.com/smartdatalab/public/ci-cd-components/renovate/commit/37f1acad5097a5021b4efd7505be1a4f4288a503))

### Features

* add $CI_SERVER_FQDN as Renovate registryAlias ([b9705d55](https://git.code.tecnalia.com/smartdatalab/public/ci-cd-components/renovate/commit/b9705d55b2709bbfe84d88d3575e41602b47adcb))

# Conflicts:
#	.gitlab-ci.yml
#	CHANGELOG.md
#	README.md
#	kicker.json
#	templates/gitlab-ci-renovate.yml

# [1.3.0](https://gitlab.com/to-be-continuous/renovate/compare/1.2.2...1.3.0) (2024-08-23)

### Bug Fixes

* remove RENOVATE_PLATFORM as configurable param ([37f1acad](https://gitlab.com/to-be-continuous/renovate/commit/37f1acad5097a5021b4efd7505be1a4f4288a503))

### Features

* add $CI_SERVER_FQDN as Renovate registryAlias ([b9705d55](https://gitlab.com/to-be-continuous/renovate/commit/b9705d55b2709bbfe84d88d3575e41602b47adcb))

Merge branch '2-be-able-to-update-component-with-ci_server_fqdn-variable-in-component-path' into 'master'

Resolve "be able to update component with CI_SERVER_FQDN variable in component path"

Closes #2

See merge request to-be-continuous/renovate!10

# Conflicts:
#	.gitlab-ci.yml

chore(deps): update dependency to-be-continuous/semantic-release to v3.11

See merge request to-be-continuous/renovate!8

chore(deps): update dependency to-be-continuous/semantic-release to v3.10

See merge request to-be-continuous/renovate!7

## [1.2.2](https://git.code.tecnalia.com/smartdatalab/public/ci-cd-components/renovate/compare/1.2.1...1.2.2) (2024-05-21)

### Bug Fixes

* **workflow:** disable MR pipeline from prod & integ branches ([e32e815f](https://git.code.tecnalia.com/smartdatalab/public/ci-cd-components/renovate/commit/e32e815f6aa487edf0c25112cc6173bbd1ce0ad2))

## [1.2.2](https://gitlab.com/to-be-continuous/renovate/compare/1.2.1...1.2.2) (2024-05-05)

### Bug Fixes

* **workflow:** disable MR pipeline from prod & integ branches ([e32e815f](https://gitlab.com/to-be-continuous/renovate/commit/e32e815f6aa487edf0c25112cc6173bbd1ce0ad2))

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

## [1.2.1](https://gitlab.com/to-be-continuous/renovate/compare/1.2.0...1.2.1) (2024-2-5)

### Bug Fixes

* set platform to gitlab ([df1894cb](https://gitlab.com/to-be-continuous/renovate/commit/df1894cb110a180bd871185fa3585b78588b23ba))

fix: set platform to gitlab by default

See merge request to-be-continuous/renovate!6