Author	SHA1	Message	Date
Andrew Nesbitt	8e04713425	Use shared registries size limits and rate-limit gate (#516) ... * Use shared registries size limits and rate-limit gate * Use registries v0.10.0 release	2026-10-19 13:28:55 +02:00
simon chrzanowski	b7b7a64239	Add a size limit for upstream artifacts ... Artifacts had no size limit. A fetch was bounded only by the server's write timeout, and storage.max_size evicts only after the bytes are written, so any client could fill storage or keep fetches busy by requesting huge artifacts. - Add artifact_max_size (PROXY_ARTIFACT_MAX_SIZE), unlimited by default - Refuse an artifact whose declared size is over the limit before reading it, and fail one of unknown size once the download passes the limit - Apply it in the fetcher so stored, streamed and mirrored artifacts all honour it; nothing is cached and clients get 502	2026-10-14 08:41:57 +02:00