mirror of
https://github.com/renovatebot/renovate.git
synced 2026-10-25 15:01:49 +00:00
Jamie Tanna
8b3a066756
As we're now managing them via a `afterEach` in `test/setup.ts`, we can remove any entries in tests themselves. We don't update overrides of an outer hook or cases where there are more explicit `clear()`s. Co-authored-by: Claude Sonnet 5 <jamie.tanna+claude-code@mend.io>
This datasource uses the following logic to determine lookup URLs:
- If the normalized registryUrl ends in
/simple/or/+simple/then only the simple API will be tried - Otherwise, the JSON API will be tried first
- If the JSON API returns a result, it will be used
- If the JSON API throws an error (e.g. 403, 404) then the simple API will be tried
The Simple API supports both the HTML serialization (PEP 503) and the JSON serialization (PEP 691).
Renovate uses content negotiation (an Accept header) to prefer the JSON serialization, falling back to HTML automatically if the registry does not support it.
If the registry responds 406 because it cannot serve any of the negotiated types, Renovate retries the request without that header.
Renovate reads the release timestamp from the upload_time of a version's files, or the upload-time (PEP 700), which the Simple JSON API exposes, so minimumReleaseAge works against it.
If you are using Artifactory, you must explicitly enable the generation of upload-time metadata server-side.