# [2.6.0](https://git.code.tecnalia.com/smartdatalab/public/ci-cd-components/gitleaks/compare/2.5.2...2.6.0) (2024-08-29)

### Features

* default gitleaks arguments to avoid secret exposure ([595fc7df](https://git.code.tecnalia.com/smartdatalab/public/ci-cd-components/gitleaks/commit/595fc7dfe42fd00c8c5dc6647779bed24955e0f4))

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

# [2.6.0](https://gitlab.com/to-be-continuous/gitleaks/compare/2.5.2...2.6.0) (2024-07-15)

### Features

* default gitleaks arguments to avoid secret exposure ([595fc7df](https://gitlab.com/to-be-continuous/gitleaks/commit/595fc7dfe42fd00c8c5dc6647779bed24955e0f4))

feat: default gitleaks arguments to avoid secret exposure

See merge request to-be-continuous/gitleaks!52

# Conflicts:
#	.gitlab-ci.yml

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

See merge request to-be-continuous/gitleaks!51

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

See merge request to-be-continuous/gitleaks!50

## [2.5.2](https://git.code.tecnalia.com/smartdatalab/public/ci-cd-components/gitleaks/compare/2.5.1...2.5.2) (2024-05-20)

### Bug Fixes

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

## [2.5.2](https://gitlab.com/to-be-continuous/gitleaks/compare/2.5.1...2.5.2) (2024-05-05)

### Bug Fixes

* **workflow:** disable MR pipeline from prod & integ branches ([3d43c7f9](https://gitlab.com/to-be-continuous/gitleaks/commit/3d43c7f96d6e623bf20df17f0302b2dbe22b6fa2))

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

## [2.5.1](https://gitlab.com/to-be-continuous/gitleaks/compare/2.5.0...2.5.1) (2024-03-31)

### Bug Fixes

* **verbose:** restore verbose by default as otherwise found secrets aren't printed in the console ([367a84ce](https://gitlab.com/to-be-continuous/gitleaks/commit/367a84ce6548f0c529e7b555ca16a821474c3472))

this is a partial revert

# [2.5.0](https://gitlab.com/to-be-continuous/gitleaks/compare/2.4.1...2.5.0) (2024-03-31)

### Features

* **verbose:** verbose is no longer the default ([4db5301a](https://gitlab.com/to-be-continuous/gitleaks/commit/4db5301a24cb7f7f87d040be3e3234d13b4b7754)), closes [#17](https://gitlab.com/to-be-continuous/gitleaks/issues/17)

fixes #17

- verbose is no longer the default
- automatically enabled when $TRACE is set
- removed unused quick parameters (no longer supported)

chore(deps): update to-be-continuous dependencies

See merge request to-be-continuous/gitleaks!49

## [2.4.1](https://gitlab.com/to-be-continuous/gitleaks/compare/2.4.0...2.4.1) (2024-1-31)

### Bug Fixes

* remove install_ca_certs ([86464e61](https://gitlab.com/to-be-continuous/gitleaks/commit/86464e616d6b6db98df659af8ff90e9554bfdeb9))

fix: remove install_ca_certs

Closes #16

See merge request to-be-continuous/gitleaks!48

# [2.4.0](https://gitlab.com/to-be-continuous/gitleaks/compare/2.3.0...2.4.0) (2024-1-27)

### Features

* migrate to CI/CD component ([e15efce4](https://gitlab.com/to-be-continuous/gitleaks/commit/e15efce410230f21d5e5eba052413996d832559d))

feat: migrate to CI/CD component

See merge request to-be-continuous/gitleaks!47

 requires GitLab 16.6 or later

chore(deps): update to-be-continuous dependencies

See merge request to-be-continuous/gitleaks!46

# [2.3.0](https://gitlab.com/to-be-continuous/gitleaks/compare/2.2.3...2.3.0) (2023-12-8)

### Features

* use centralized tracking image (gitlab.com) ([37ccee87](https://gitlab.com/to-be-continuous/gitleaks/commit/37ccee878bf8f24374d6179a0716ca76e8935601))