Michael Kriese
3a723b7891
* test(versioning/aws-machine-image): cover the empty version guard `_parse()` returns null for a falsy version before it tries the AMI id regex, and no test passed one. Checking that an empty string is not valid closes the only branch the module was missing. Co-Authored-By: Claude Opus 5 <michael.kriese+claude-code@mend.io> * test(datasource/buildpacks-registry): cover a response without a homepage `latest.homepage` is optional in the registry response, but every test supplied one, so the release result was never built without it. A buildpack whose latest entry carries no homepage now checks that the releases still come back and no source url is derived. Co-Authored-By: Claude Opus 5 <michael.kriese+claude-code@mend.io> * test(datasource): cover optional-field branches in four datasources Each of these datasources builds its release result by attaching fields only when the registry supplies them, and the "not supplied" path was never exercised: - cdnjs: a library with neither homepage nor repository - cpan: a search result where no release is marked latest, so no tag - dart: a latest release carrying no pubspec - ruby-version: a release table row whose first column is not a version Co-Authored-By: Claude Opus 5 <michael.kriese+claude-code@mend.io> * test(datasource): cover missing-metadata branches in hex and pypi Two more datasources only attached fields when the registry supplied them, and the absent case was untested: a hex package with neither an html_url nor a github link in its meta, and a pypi response carrying no releases at all. Co-Authored-By: Claude Opus 5 <michael.kriese+claude-code@mend.io> * test(datasource): cover galaxy and repology fallbacks, mark unreachable guards Adds a galaxy role with empty github fields, so no source url is derived, and a repology lookup where the api fallback after a 403 finds no matching package. Marks four guards that are not worth a test: cpan and dart both check a variable that is only null when the request threw, and `handleGenericErrors()` always rethrows; conan's registry url is always supplied by the datasource layer; and repology's resolver either returns a body or throws. Co-Authored-By: Claude Opus 5 <michael.kriese+claude-code@mend.io> * test(datasource): cover pod CDN branches, mark the sbt listing guards Adds two pod lookups: an empty CDN body, and a CDN index that lists no matching pod. Marks the guards whose tests would need multi-level directory listing fixtures: both sbt datasources walk nested index pages, and pod's github helper checks a body that an empty json response never produces because parsing throws first. Co-Authored-By: Claude Opus 5 <michael.kriese+claude-code@mend.io> * test(datasource): cover maven metadata without a latest tag Adds maven metadata carrying a release but no latest, so respectLatest is left alone. Marks the three deb guards, which would each need a crafted package index: a block missing a required key, a repeated package in the final block, and two component indexes whose meta agrees. Co-Authored-By: Claude Opus 5 <michael.kriese+claude-code@mend.io> * test(datasource): cover npmrc registry fallback, mark cache-bound guards Adds a resolveRegistryUrl lookup for a package no npmrc rule matches. Marks the guards whose tests would need a primed cache or a specific blob shape: nuget's services index, deno's release cache, the docker hub cache window, docker's manifest and config handling, go's pseudo-version fallback, and both rubygems cache layers. Three implicit elses are left counted: a coverage-ignore hint does not attach to an `else if`, so the registry strategy chain, the npmrc reset and docker's digest-header branch carry a plain note instead. Co-Authored-By: Claude Opus 5 <michael.kriese+claude-code@mend.io> * fix(datasource/repology): pass the mock body as a string `ResponseMock.body` is typed as a string, and every other call in the spec passes `'[]'`. The new api fallback test passed an array literal, which tsc rejected. Co-Authored-By: Claude Opus 5 <michael.kriese+claude-code@mend.io> --------- Co-authored-by: Claude Opus 5 <michael.kriese+claude-code@mend.io>
With Repology you can look up package versions from many package repositories. You can combine Repology with regex managers to update dependencies which are not supported by Renovate.
The packageName field should be constructed using the repository identifier and the actual package name separated by a slash.
For example: alpine_3_12/gcc would look for a binary (or source package) called gcc within the alpine_3_12 repository.
A list of all supported repositories can be found on the Repology homepage.
To find the correct identifier, select the repository you want and copy the identifier in the URL: https://repology.org/repository/<identifier>.
For example, the Alpine Linux 3.12 repository has this URL: https://repology.org/repository/alpine_3_12 and has this repository identifier: alpine_3_12.
Usage Example
Say you're using system packages in a Dockerfile and want to update them with Repology. With the Repology datasource you can "pin" each dependency, and get automatic updates.
First you would set a custom manager in your renovate.json file for Dockerfile:
{
"customManagers": [
{
"customType": "regex",
"managerFilePatterns": ["/^Dockerfile$/"],
"matchStrings": [
"#\\s*renovate:\\s*datasource=(?<datasource>.*?) depName=(?<depName>.*?)( versioning=(?<versioning>.*?))?\\sENV .*?_VERSION=\"(?<currentValue>.*)\"\\s"
],
"versioningTemplate": "{{#if versioning}}{{{versioning}}}{{else}}semver{{/if}}"
}
]
}
Then you would put comments in your Dockerfile, to tell Renovate where to find the updates:
FROM alpine:3.12.0@sha256:a15790640a6690aa1730c38cf0a440e2aa44aaca9b0e8931a9f2b0d7cc90fd65
# renovate: datasource=repology depName=alpine_3_12/gcc versioning=loose
ENV GCC_VERSION="9.3.0-r2"
# renovate: datasource=repology depName=alpine_3_12/musl-dev versioning=loose
ENV MUSL_DEV_VERSION="1.1.24-r8"
RUN apk add --no-cache \
gcc="${GCC_VERSION}" \
musl-dev="${MUSL_DEV_VERSION}"
When the operating system package for gcc of Alpine Linux 3.12 is updated, Renovate updates the environment variable.
!!! tip
We recommend you try loose or deb versioning for distribution packages first.
This is because the version number usually doesn't match Renovate's default semver-coerced specification.