Skip to content

manager(gitlabci): do not skip ~latest version #44713

Description

@RahulGautamSingh

Discussed in #43356

Originally posted by jr-elliott May 14, 2026

How are you running Renovate?

Self-hosted Renovate CLI

Which platform you running Renovate on?

GitLab (.com or self-hosted)

Which version of Renovate are you using?

41.173.1

Please tell us more about your question or problem

A lot of our .gitlab-ci.yml file have components included with the ~latest tag:

include:
  - component: $CI_SERVER_HOST/ci-catalog/iac/plan@~latest

From my understanding of the Renovate docs, this is considered partial semantic versioning and it should resolve to a full semantic version.

However, our Renovate runs are skipping these components entirely. I checked the Gitlab CI manager source code and it seems intentional to skip over ~latest.

Am I misconfiguring something somewhere? Is there a way to get Renovate to pin the version of the component?

Thank you.

Logs (if relevant)

Logs

               {
                 "datasource": "gitlab-tags",
                 "depName": "ci-catalog/promotion",
                 "depType": "repository",
                 "currentValue": "~latest",
                 "registryUrls": ["https://${CI_SERVER_HOST}"],
                 "versioning": "semver-partial",
                 "skipReason": "unsupported-version",
                 "updates": [],
                 "packageName": "ci-catalog/promotion"
               },

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    Fields

    Priority

    Medium

    Datasource

    None yet

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions