The `.tool-versions` file is governed by two managers: `regex` and `asdf`.

So far, adding a `datasource`/`depName` comment *enables* the `regex` manager
with a custom regular expression. However, it does not *disable* the `asdf`
manager. That means that the `asdf` manager may still upgrade a tool, even when
the (more explicitly configured) `regex` manager would not.

For example, gitlab-com/gl-infra/platform/runway/provisioner!663 tried to
upgrade `tflint` due to a GitHub release, despite the explicitly provided
`datasource` not having the new version yet.

With this change the following syntax will do what we need:

```
tflint 0.55.1 # renovate:ignore # datasource=docker depName=registry.gitlab.com/gitlab-com/gl-infra/common-ci-tasks-images/tflint
```

* The `regex` manager will continue to parse this line as it has before – the
  `renovate:ignore` has no meaning for it.
* The `asdf` manager will honor the `renovate:ignore` marker and ignore the
  dependency.

Minor unrelated fix: the regular expression previously anchored on a trailing
newline `\n`. This is problematic when the file does not have a newline at the
end-of-file, which is a common behavior for code editor unfortunately. This
enables multi-line mode (`(?m)`), so `$` also matches at the end-of-line, and
uses `$` instead of `\n` for the end-of-line match.

feat(renovate): Add support for `renovate:ignore` in `.tool-versions`.

See merge request !988

## [2.71.0](https://gitlab.com/gitlab-com/gl-infra/common-ci-tasks/-/compare/...) (2025-04-04)

### Features

* **renovate:** Add support for `renovate:ignore` in `.tool-versions`. ([c7034d48](c7034d48))

Instead, we use a central database for lookups, giving easier control.

chore: EXPERIMENTAL remove Renovate annotations from tool-versions

See merge request !989

chore(deps): update pre-commit hook gitlab-com/gl-infra/common-ci-tasks to v2.71

See merge request !990

Releasing on Default Branch

By default, the Goreleaser task will release on tag CI pipelines.
In some cases, it may be necessary to release on CI pipelines to the
default branch.

This can be configured by setting `GORELEASER_RELEASE_ON_DEFAULT_BRANCH=1`

```yaml
variables:
    GORELEASER_RELEASE_ON_DEFAULT_BRANCH: 1
```

fix: add ability to gorelease on main branch

See merge request !991

## [2.71.1](https://gitlab.com/gitlab-com/gl-infra/common-ci-tasks/-/compare/...) (2025-04-09)

### Fixes

* add ability to gorelease on main branch ([a3767242](a3767242))

### Others

* EXPERIMENTAL remove Renovate annotations from tool-versions ([cb67292a](cb67292a))

### Dependencies

* **deps:** update pre-commit hook gitlab-com/gl-infra/common-ci-tasks to v2.71 ([f5707ca5](f5707ca5))

Unfortunately goreleaser objects to releasing on the main branch as
there is no tag.

For the cases in which we're using this mode, that's not a problem, so
we add the `--skip=validation` flag to `goreleaser release` to allow it
to continue.

fix: skip validation for GORELEASER_RELEASE_ON_DEFAULT_BRANCH

See merge request !992

## [2.71.2](https://gitlab.com/gitlab-com/gl-infra/common-ci-tasks/-/compare/...) (2025-04-10)

### Fixes

* skip validation for GORELEASER_RELEASE_ON_DEFAULT_BRANCH ([6c3460ed](6c3460ed))

goreleaser uses Git commit to dertmine the semantic version it should release.
Running it on other tags on the same commit results in two goreleaser jobs
racing each other.

Issue: production-engineering#26615

fix(goreleaser): Only run on semantic version tags.

See merge request !993

## [2.71.3](https://gitlab.com/gitlab-com/gl-infra/common-ci-tasks/-/compare/...) (2025-04-11)

### Fixes

* **goreleaser:** Only run on semantic version tags. ([fb11c454](fb11c454)), closes [production-engineering#26615](https://gitlab.com/gitlab-com/gl-infra/production-engineering/-/issues/)