renovate

mirror of https://github.com/renovatebot/renovate.git synced 2026-11-02 10:33:39 +00:00

Files

T

History

Sebastian Poxhofer 05e1271376 test: use expect().resolves instead of awaiting inside expect (#45672 )

Enables the vitest/prefer-expect-resolves oxlint rule and applies its
autofix across the spec suite.

2026-09-04 10:40:46 +00:00

index.spec.ts

test: use expect().resolves instead of awaiting inside expect (#45672 )

2026-09-04 10:40:46 +00:00

index.ts

fix(linters): forbid inert counts in v8 coverage-ignore comments (#45287 )

2026-08-22 11:25:31 +00:00

readme.md

feat(config): managerFilePatterns (#34615 )

2025-05-04 08:30:24 +00:00

types.ts

refactor: lib/modules (#14488 )

2022-03-04 09:04:02 +01:00

readme.md

GitLab Releases API supports looking up releases supported by GitLab and can be used in combination with regex managers to keep dependencies up-to-date which are not specifically supported by Renovate.

To specify which specific repository should be queried when looking up a package, the packageName should be set to the project path.

As an example, gitlab-org/ci-cd/package-stage/feature-testing/new-packages-list would look for releases in the gitlab-org/ci-cd/package-stage/feature-testing/new-packages-list project.

To specify where to find a self-hosted GitLab instance, specify registryUrl. An example would be https://gitlab.company.com.

Please note the following requirements:

This datasource requires at least GitLab 11.7

Usage Example

A real-world example for this specific datasource would be maintaining package versions in a config file. This can be achieved by configuring a custom manager in renovate.json for files named versions.ini:

{
  "customManagers": [
    {
      "customType": "regex",
      "managerFilePatterns": ["/^versions.ini$/"],
      "matchStrings": [
        "# renovate: datasource=(?<datasource>.*?) depName=(?<depName>.*?)( versioning=(?<versioning>.*?))?( registryUrl=(?<registryUrl>.*?))?\\s.*?_VERSION=(?<currentValue>.*)\\s"
      ],
      "versioningTemplate": "{{#if versioning}}{{{versioning}}}{{else}}semver{{/if}}"
    }
  ]
}

Now you may use comments in your versions.ini files to automatically update dependencies, which could look like this:

# renovate: datasource=gitlab-releases depName=gitlab-org/ci-cd/package-stage/feature-testing/new-packages-list versioning=semver registryUrl=https://gitlab.com
NKJS_VERSION=3.4.0

By default, gitlab-releases uses the semver-coerced versioning scheme.