5de58da4b7
listTags() follows the registry's Link-header pagination, but the next-page URL is relative per the OCI/Docker registry spec (e.g. "/v2/ollama/ollama/tags/list?last=0.9.3-rc5&n=1000"). The code assigned that raw relative path straight back to `url` and re-fetched it, so fetch() threw "Failed to parse URL from /v2/...". Any image repo with more than 1000 tags paginates, so the entire tag list — and therefore the update check — failed silently for ollama/ollama and filebrowser/filebrowser. That's the root cause of #945 ("won't update past 0.24.0"): the Ollama update check never completed, so no newer version was ever offered. Resolve the next-page URL against the registry origin with new URL(next, `https://${registry}`), which also passes absolute next-URLs through unchanged for registries that return those. Closes #945 |
||
|---|---|---|
| .. | ||
| controllers | ||
| exceptions | ||
| jobs | ||
| middleware | ||
| models | ||
| services | ||
| utils | ||
| validators | ||