* fix(docker): handle 405 maxResults error on auth probe for ECR-compatible proxies Some private Docker registries that front ECR reject `n=10000` on the tags URL even during the auth-probe request, returning a 405 with the ECR-style "Member must have value less than or equal to 1000" error body. `getAuthHeaders` had no handler for this case and returned null, so the lookup aborted before the main fetch loop's existing n=1000 retry could fire. Fix: extract `isECRMaxResultsResponse` from `isECRMaxResultsError` in ecr.ts and use it in `getAuthHeaders` to detect the 405 pattern. When matched, fall back to probing the base `/v2/` endpoint for auth, then let the existing `isECRMaxResultsError` retry in the tag-fetch loop handle the n=1000 fallback. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * fix(docker): address PR review comments on ECR proxy auth probe fix - Shorten test token to 'abc' to avoid CodeQL secret-detection false positive - Replace HttpResponse<any> with HttpResponse<unknown> in common.ts and ecr.ts Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * fix(docker): replace HttpResponse<any> with HttpResponse<unknown> in isECRMaxResultsResponse Cast body to a typed shape inline instead of widening the whole response to any. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * test(docker): replace toMatchInlineSnapshot with toEqual in ECR auth probe test Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> --------- Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
Datasources
Datasources are used in Renovate primarily to fetch released versions of packages.
Follow the class-based programming style
New datasources must follow the class-based programming style.
Use the java-version datasource as a reference.
Add the datasource to the API in api.ts so that the new datasource is usable.
If you find Unused HTTP mocks errors in the Vitest tests and your mocked URLs are correct, make sure the datasource is correctly registered.
getReleases
The minimum exported interface for a datasource is a function called getReleases that takes a lookup config as input.
The config has:
packageName: the package's full name including scope if present (e.g.@foo/bar)registryUrls: an array of registry URLs to try
getReleases should return an object having:
releases: an array of strings of matched versions. This is the only mandatory fielddeprecationMessage: a string description of the package's deprecation notice, if applicablesourceUrl: a HTTP URL pointing to the source code (for example on GitHub)homepage: a HTTP URL for the package's homepage. Ideally should be empty if the homepage andsourceUrlare the samechangelogUrl: a URL pointing to the package's changelog (could be a Markdown file, for example). If not present then Renovate will search thesourceUrlfor a changelog filetags: an object mapping tag → version, for exampletags: { latest: '3.0.0' }. This is only used by thefollowTagsfunction
getDigest
Datasources that support digests (like Docker digests and Git commit hashes) can export a getDigest function.
The getDigest function has two inputs:
config: the Renovate config for the package being updated, has the same fields asgetReleasesnewValue: the version or value to retrieve the digest for
The getDigest function returns a string output representing the digest value.
If no digest is found, the getDigest function should return null.