Changelog

Virtual Registry 0.18.0 #

Released: 2026-09-10

Varnish version: 6.0.18r4

Artifact Firewall version: 0.6.0

Added#

• Added cluster.storage_replicas, which shards persistent storage across the cluster instead of replicating it. A clustered node caches every object it serves in memory and persists it to disk as well, so a cluster of N nodes holds N copies on disk and its usable persistent cache is that of a single node. Setting storage_replicas: 1 keeps each object on disk only on the node that owns it, pooling the whole cluster’s disk into one cache; a higher count keeps that many copies, trading capacity back for redundancy. Unset it stays full replication. Requires the persistence addon and configured varnish.storage.stores.
• Added RPM (yum/dnf/zypper) support: .rpm packages and the checksum-named repodata files are cached for the immutable lifetime, repomd.xml revalidates, and where the firewall is enabled repomd.xml and primary.xml are filtered while a .rpm download is authorized per version. Filtering repomd.xml invalidates its signature, so the client needs repo_gpgcheck=0 (per-package gpgcheck=1 keeps working), or firewall.preserve_manifest: true to keep the upstream signature and give up metadata filtering.
• Go modules now go through the firewall where it is enabled: @v/list is filtered to the versions the ruleset allows, @latest, .info and .mod are gated on the version they resolve to, and a module zip is authorized per version. The checksum database is not a module resource and is untouched.
• Conda channels now go through the firewall where it is enabled: repodata.json is filtered to the packages the ruleset allows, and a .conda or .tar.bz2 download is authorized per version. The two variants the firewall cannot filter, repodata.json.bz2 and CEP-16 sharded repodata, are refused so the client falls back to one it can.
• The startup line and --version now carry the revision the binary was built from, as stamped by the Go toolchain, suffixed -dirty for a build off a modified tree. It is omitted when the build carries no stamp.
• Added ArgoCD UI proxying: the UI and its Dex/OIDC login flow get a full cache bypass and a redirect-follow opt-out, the same treatment already given to the JFrog UI, so the login’s session cookie isn’t dropped by a server-side redirect.
• Added the /package-reroute endpoint (virtual_registry.package_reroute.enabled, off by default): a network-redirect target for a forward proxy that intercepts outbound traffic to public package registries, such as a Zscaler ZIA rule mirroring JFrog’s Package Traffic Controller. It resolves the upstream host embedded in ?url= against every configured registry’s remotes and re-enters that registry’s normal pipeline.
• Added Ubuntu 26.04 (Resolute Raccoon) packages. The .deb is the same build already published for the other Debian-family distributions; it is now uploaded to, and installed and upgraded under, ubuntu/resolute as well.
• Added an optional name to a remote (virtual_registry.registries[].remotes[]) and a cluster peer (cluster.peers[]), used in the generated backend/director name instead of a positional index. Both share the same underlying config type, so the fix covers artifactory_dir_N and cluster_dir_N alike. Names are alphanumeric and hyphens only, and must be unique within their list; an unnamed remote or peer keeps the existing positional naming.

Changed#

• remote_auth now applies to every package type, not just OCI (Docker/container) registries. For OCI it still targets the /token auth-token exchange; for everything else it is attached to the content request itself, in vcl_recv, and an injected request is classified as its own cache entry rather than preflighted, since the caller’s own credential is not what reaches the remote. That entry is shared by every injected caller and keyed without the credential, so rotating the secret in password_env leaves the cached objects in place instead of invalidating them. policy: always combined with auth_policy: preflight therefore skips the preflight check, which a startup warning now calls out. if_anonymous is unaffected: it still only fills in when the caller sent no credential of its own.
• Reworked what the Supervisor logs. Startup records the Supervisor, varnishd and add-on versions, the config files it read, and the configuration itself as every setting that differs from the defaults, so a log says what a Supervisor was running without its files having to be found. A reload names the settings that changed instead of counting them, and INFO is reserved for state changes rather than a line before and another after each one. The license text and its signature are no longer written to the log when they change, and the container image no longer echoes the versions before startup, since the Supervisor reports them itself.
• Removed the startup warning about virtual_registry.redirects.deny_unknown_hosts not being set. It fired on every configuration that left the option at its default, and writing the default out verbatim was the only way to silence it.
• The varnish-supervisor package now installs a Varnish module, /usr/lib/varnish-plus/vmods/libvmod_vizier.so, which the generated VCL imports. Hex requests are now parsed inside that module. Every other ecosystem is unchanged, and caching behaviour behaves the same regardless of it is parsed by the VMOD. Remaining ecosystems will move across one at a time. A Varnish module is ABI-bound to the exact Varnish Enterprise build it was compiled against, so varnish-plus and varnish-supervisor must now be upgraded together. Upgrading varnish-plus alone leaves Varnish unable to load its VCL.

Fixed#

• Fixed a firewall rule scoped to a set of virtual registries never matching a package download. The check that authorizes a download did not name the registry it was made for, and a scoped rule matches nothing without one, so the rule was skipped and the download allowed. Rules that are not registry-scoped, and the filtering of index and metadata documents, were unaffected.
• Fixed the version of an npm tarball being read from the first hyphen in its filename, so a package whose name contains one was authorized and audit-logged under a mangled version: map-stream-0.0.7.tgz came out as version stream-0.0.7. A rule scoped to a version range could deny a version it allows, or allow one it denies.
• Fixed supervisor.log_level and supervisor.log_output only taking effect for the config manager itself on reload. Every other component kept the settings it started with, and a change to log_output silenced them for the rest of the run, since the file they were still writing to had been closed. A reload and a SIGHUP now also wait for the records already on their way into the old file before closing it.
• Fixed the reload line reporting unrelated registries as changed when one was removed from the middle of the list. Registries and stores are now matched by name rather than by position, and the list itself is reported when its members or their order change, the order being what the generated routing rules are built from.
• Fixed a varnishd message that runs over several lines losing everything after the first line when it followed one of the startup milestones.
• Fixed a cached certificate entry that could not be deleted being reported as cleared. The failure is now logged, since an entry left behind is read back by the next fetch.
• Fixed a change to acme.domains that swaps one domain for another, rather than adding or removing one, not reaching ACME. The reload applied, but no certificate was requested for the new domain until the Supervisor was restarted.
• Fixed the OpenTelemetry pipeline being started before Varnish, so it spent the first seconds of every startup warning that the shared log it reads was not there yet.
• Fixed a redirect from a remote being followed with the original request’s path instead of the path the redirect pointed at, on deployments with clustering enabled. Any remote that signs its redirect targets rejected the resulting fetch, which made every ghcr.io layer pull fail with 400 Missing query parameters.
• Fixed PyPI wheel and sdist downloads not being authorized against the firewall, so a client holding the URL already, from a lock file or a cached index, was served a version a rule denies. The download is now checked per version, as it is for every other ecosystem.
• Fixed Maven .pom files at a released version revalidating against the remote on every request, which cost a round trip per descriptor in a resolve. They are now cached for the immutable lifetime, while .pom files under a -SNAPSHOT version keep revalidating.
• Fixed the systemd scriptlets in the varnish-supervisor RPM, which never ran. An install only logged a warning, but an upgrade failed the transaction and left both versions recorded as installed. Upgrading from 0.17.0 or earlier still trips on the old package’s own scriptlets: run the upgrade again, then drop the stale record with rpm -e --noscripts varnish-supervisor-<old version> and restart the service.
• Fixed a DEB upgrade re-enabling and starting the Supervisor where it had deliberately been disabled or stopped. An upgrade now restarts it only if it was already running. Upgrading from 0.17.0 or earlier is the exception, and still enables and starts it: those versions stop and disable the unit from their own prerm, which runs before anything in the new package does, so there is no state left to preserve.
• Fixed systemctl stop varnish-supervisor leaving the service in a failed state. Varnish was killed outright instead of being asked to stop, which also meant the shutdown_delay and shutdown_close parameters never took effect.
• Fixed the Supervisor hanging until systemd killed it when it was stopped while a varnishadm command was still in flight, which is most likely when the service is stopped shortly after it starts.

Virtual Registry 0.17.0 #

Released: 2026-08-25

Varnish version: 6.0.18r4

Artifact Firewall version: 0.5.1

Added#

• Added support for caching Conda artifacts, including the channel index, CEP-16 sharded repodata (conda 26+), and .conda / .tar.bz2 packages. The conda, mamba and micromamba clients are recognised.
• Added remote_auth to virtual registries, letting operators configure a shared credential (username/password_env) that Orca attaches to outbound requests to the remote on the client’s behalf. Currently only implemented for OCI (Docker/container) registries, targeting the /token auth-token exchange. Inactive until remote_auth.policy is set: always replaces any credential the client sent (so pulls through that registry count against the configured account’s rate limit instead of the upstream’s shared anonymous quota), or if_anonymous, which only fills in when the client sent no credential of its own, leaving an existing one untouched. Not scope-aware, so give the configured credential read-only permissions upstream. Independent of auth_policy, except that it is not valid combined with auth_policy: drop.
• Added retry_statuses to virtual registries, the response statuses from a remote that send the fetch to a remote it has not used yet. Valid values are 400-499 except 401 and 407, whose challenges have to reach the client. Set retry_statuses: [] to keep the first remote’s response instead. The retries spend the same max_retries budget as the 5xx and connection retries, so raise that varnishd parameter for a registry with more remotes than it allows.
• Orca now serves the Go checksum database at /sumdb/<name>/..., so GOPROXY is the only setting a client needs and checksum verification keeps working where the go command has no route to sum.golang.org of its own. Only the two databases the go command ships with are proxied.

Changed#

• A registry with more than one remote now retries a 404 or a 429 against a remote the request has not been sent to yet, so an artifact only one of them holds is still served, and a remote that throttles is spent on one that does not. The client gets the response of the last remote asked. This is the new default for every such registry, configurable per registry with retry_statuses above.
• A cluster node self-routing a request no longer repeats the sending node’s preflight authorization check against origin; it trusts that peer’s already-settled decision instead, verified via the existing cluster token. This removes a redundant round-trip to origin for every authorized cluster request.

Fixed#

• Fixed vcl.load timing out at a fixed 30 seconds regardless of cli_timeout. Supervisor’s command timeout is now derived from it.
• Fixed manifest requests potentially being served from a cache entry shared across different authorized users, when the origin restricts what each user is allowed to see. Each authorized user now gets their own cache entry for manifests.
• Fixed a remote’s 5xx being replaced by a synthetic 503 when the retry it triggered had no remote left to go to. The status and body the remote actually sent were discarded, which for a client parsing JSON turns an upstream outage into an unrelated parse error. The remote’s own response is now delivered, or a stale object where one exists.
• Fixed the JFrog UI and OAuth flows having their redirects followed server-side, which consumed the session cookie bound to the 3xx and could break SSO. The opt-out those paths ask for never reached the code that follows redirects.
• Fixed a fetch that followed a relative redirect being stuck with the remote that issued it, on registries with more than one remote. A 5xx, a failed connection, or a 404 at the redirected path kept asking that same remote for a path only it knew about. The retry now goes to another remote and asks for the URL the client sent.
• Fixed digest-addressed OCI manifests and blobs being shared across repositories without a matching authorization check, so a client authorized for one image could be served cached content belonging to an image it has no access to. Preflight authorization is now scoped to the repository and the digest together.
• Fixed preflight authorizations being shared between virtual registries for content-addressed artifacts, so a virtual registry that granted access spoke for every other virtual registry serving the same artifact. Each virtual registry’s access control is now enforced on its own.
• Fixed tag-addressed OCI manifests being cached without regard to the media type the client asked for, so a client accepting only OCI types could be served a Docker-media-type manifest. Tagged manifests now vary on Accept. Manifests referenced by digest are unaffected.
• Fixed Go module proxy @latest requests not being recognised as Go, so they were cached as an unknown resource type instead of as a mutable manifest.
• Fixed Go modules published at major version 2 or above being classified as OCI, since their module path contains a /v2/ segment.

Virtual Registry 0.16.0 #

Released: 2026-08-04

Varnish version: 6.0.18r3

Artifact Firewall version: 0.4.0

Added#

• Added auth_policy option to virtual registries, letting operators skip or actively strip preflight authorization checks on backends that already permit anonymous access. preflight (default) keeps today’s behavior of verifying every request via a HEAD check; ignore skips the check and shares cache with anonymous requests while still forwarding Authorization unchanged to the backend; drop strips Authorization before it ever reaches the backend.
• Added auth_token_ttl to virtual registries (default 60s). Orca now caches OCI auth tokens per credential and scope for this window and hands the same bearer token back, keeping the downstream authorization cache key stable so already-cached images keep serving while the upstream registry or its token endpoint is unreachable (the cached token and preflight are revived for up to 1 week). Set auth_token_ttl: 0 to disable and pass token requests straight through. Only active when the Authentication feature is licensed.
• Improved support for caching Cargo (Rust) artifacts served over the sparse registry protocol. This includes the registry config.json, the package index, and .crate downloads.
• Added support for caching Hex (Erlang/Elixir) artifacts, including package metadata, tarballs and doc tarballs, both against repo.hex.pm directly and through a JFrog Artifactory Hex repository. Firewall rules are enforced on the tarball download rather than by filtering the package metadata, which Hex signs and clients verify.
• Added runtime config reload. Config changes are now applied automatically when the files change on disk (supervisor.config_watch, enabled by default with a 15 second interval) or on demand with SIGHUP, and when the change affects the generated VCL, Varnish switches to it atomically without restarting, so the cache survives. Settings that require a restart are refused and leave the running config in place, and under Kubernetes the ConfigMap has to be mounted as a directory rather than with subPath, which is never updated in place.
• Added cluster.extra_tokens, a list of additional tokens accepted from peers alongside cluster.token. This lets a cluster token be rotated with a rolling redeploy (stage the new token in extra_tokens, promote it to token, then retire the old value) instead of a coordinated restart of every node at once.

Changed#

• Maven firewall rules are now enforced on the artifact download (.jar, .war, .aar, .zip) instead of on the .pom, which now streams through whatever the verdict. A build blocked on a pinned version fails when it fetches the artifact rather than when it reads the descriptor, and a denied version no longer breaks the resolution of builds that never fetch it.

Fixed#

• Fixed Maven artifact downloads never matching a firewall rule when the registry is fronted behind an Artifactory repository path prefix, which was absorbed into the groupId.
• Fixed a registry with a single remote never retrying a fetch that failed before the remote answered, so a connection the remote had already dropped reached the client as a 503. The retry now reuses the remote once when no untried remote is left.
• Fixed OCI pushes failing against a remote registry that serves on a non-default port. The upload session URL handed back to the client kept the remote’s port without its host, so the client had nowhere to send the blob.
• Fixed Git LFS batch responses not being rewritten for all clients and origins, so object downloads could bypass the cache. Note that LFS objects are fetched via /redirectz, so with redirects.deny_unknown_hosts enabled the origin’s object host must be listed in redirects.extra_known_hosts.
• Fixed Git LFS object downloads returning 404 in a clustered deployment.
• Fixed artifacts fetched through a presigned download URL being cached per signature rather than per object.
• Fixed the OCI blob HEAD existence check being cached by digest alone, so a push could skip uploading a layer another repository already cached (unknown blob). HEAD is now keyed by repository; GET stays digest-only and shared.
• Fixed the repo-scoped HEAD fix above not surviving a cluster hop, where a self-routed request normalizes to GET on the wire and could collapse back to a digest-only key. A manifest HEAD could also return Content-Length: 0 on the forwarded leg. The original request method now survives the hop and any retry to origin.
• Fixed the rendering of a remote’s dns_ttl option, which produced VCL that failed to compile.
• Fixed the error returned when redirects.deny_unknown_hosts blocks a transparent redirect target. Clients now receive the intended 502 redirect target host not allowed instead of a generic 503.
• Fixed port conflict validation reporting conflicts for address combinations that can coexist on the same port, and missing conflicts for some combinations that cannot.
• Cache PyPI PEP 658 metadata sidecars (<file>.metadata), which previously bypassed the cache.
• Cache the NuGet vulnerability data files (vulnerability.base.json and vulnerability.update.json), which previously bypassed the cache.
• Fixed the NuGet client User-Agent matching patterns.
• Added OCI client User-Agent matching patterns.
• Fixed OCI clients intermittently failing to authenticate against a clustered deployment, where a 401 challenge could carry a relative WWW-Authenticate realm instead of the absolute URL the token specification requires.

Virtual Registry 0.15.0 #

Released: 2026-07-14

Varnish version: 6.0.18r3

Artifact Firewall version: 0.3.6

Added#

• Added per-resource-type cache TTL options manifest_ttl, package_ttl, and other_ttl to virtual registries. manifest_ttl caches mutable manifests for a fixed window instead of revalidating on every request (digest-pinned manifests stay immutable); package_ttl caps the lifetime of immutable packages (mutable packages still revalidate); other_ttl sets the TTL for artifacts not classified as a manifest or package.
• Added support for Prometheus pull-based metrics scraping. When the prometheus exporter is selected via otel.metrics.exporter, Supervisor and Varnish metrics are exposed together on a /metrics scrape endpoint rather than pushed to an OTLP collector. The endpoint address is configurable via otel.metrics.prometheus_host and otel.metrics.prometheus_port (default localhost:9464).
• Added otel.metrics.scrape_interval (default 10s) to control how often varnishstat is polled for Varnish counter metrics, independent of the OTLP otel.metrics.export_interval (default 60s) push cadence.

Changed#

• The OCI /v2/ ping endpoint now has 1w keep to enable stale-if-error.

Fixed#

• Fixed clustered fetches losing the client task’s request state when a cluster self-route fails and the entry node falls back to a local origin fetch.
• Fixed the backend Host header dropping a non-standard port when following a redirect to an ad-hoc backend. goto omits the port by default, which broke signed redirects whose signature includes the port (e.g. Artifactory direct-download endpoints). The port is now preserved.
• Fixed the authenticated Git info/refs auth preflight using HEAD, which upstreams reject. This did not cause a client-visible error, but did cause a redundant fetch. It now uses GET, matching the git-upload-pack and LFS-batch preflights.
• Enforce Artifact Firewall rules when Orca fronts a Sonatype Nexus Repository (npm).

Virtual Registry 0.14.1 #

Released: 2026-07-01

Varnish version: 6.0.18r2

Artifact Firewall version: 0.3.4

Virtual Registry 0.14.0 #

Released: 2026-06-29

Varnish version: 6.0.18r2

Artifact Firewall version: 0.3.2

Added#

• Artifact Firewall support for Gradle clients (Gradle uses the Maven repository layout).

Fixed#

• Cache Ansible Galaxy collection/role downloads served over Galaxy NG / Pulp paths (e.g. JFrog Artifactory), which previously bypassed Orca.
• Decode URL-encoded slashes (%2f) in npm scoped package requests so scoped installs like npm install @scope/pkg are correctly identified by the parser.

Virtual Registry 0.13.1 #

Released: 2026-06-17

Varnish version: 6.0.18r2

Artifact Firewall version: 0.3.2

Fixed#

• Pass JFrog UI requests straight through, so flows like npm login --auth-type web are no longer misclassified as package requests and blocked.

Virtual Registry 0.13.0 #

Released: 2026-06-16

Varnish version: 6.0.18r2

Artifact Firewall version: 0.3.2

Added#

• NuGet (V3) registry support: caching and Artifact Firewall enforcement, including under JFrog Artifactory virtual repos.

Fixed#

• Enforce Artifact Firewall rules when Orca fronts a JFrog Artifactory virtual repo (npm, pypi, maven). The Artifactory path prefix previously left the firewall with incorrect package coordinates, so denied packages were allowed.

Virtual Registry 0.12.1 #

Released: 2026-06-13

Varnish version: 6.0.18r2

Artifact Firewall version: 0.3.2

Added#

• Added Virtual Registry options redirects.deny_unknown_hosts and redirects.extra_known_hosts to restrict /redirectz upstream hosts and transparent redirect targets to configured remotes and extras.

Fixed#

• Fixed /redirectz cache entries being keyed only on the path, so responses fetched from one upstream host could be served on requests targeting a different host at the same path.

Virtual Registry 0.12.0 #

Released: 2026-06-11

Varnish version: 6.0.18r2

Artifact Firewall version: 0.3.1

Added#

• Added short-lived caching of GitHub GraphQL API (POST /graphql) query responses, keyed by request body. Schema introspection queries get a longer TTL, while mutations, subscriptions, and rateLimit queries bypass the cache.
• Added preserve_host option to remotes. When enabled, the original request Host header is forwarded to the remote while the connection still targets the remote url. Useful when a single backend routes internally on the Host. Takes precedence over preserve_subdomain.
• Added virtual_registry.base_url, a default base URL applied to all registries that do not configure their own base_url.
• X-Forwarded-Proto: https from an upstream TLS terminator is now honored when auto-detecting the request scheme for base_url. Varnish also sets X-Forwarded-Proto toward the remote when the inbound request was TLS or when the registry’s base_url uses https://.

Changed#

• ACME challenge server no longer binds to port 80.
• Requests that arrive with a non-canonical Host header (a bare IPv4/IPv6 literal or localhost, e.g. clients reaching a node by IP or over a local tunnel) now have their Host rewritten to the host of the applicable base_url (registry-specific or global), so they are handled as if they had arrived at the registry’s canonical hostname.

Fixed#

• Fixed config validation preventing scheme-only base_url.
• Fixed transparent redirect-follow consuming Set-Cookie on JFrog UI and OAuth callback responses, breaking SSO login flows.

Virtual Registry 0.11.0 #

Released: 2026-06-03

Varnish version: 6.0.18r1

Artifact Firewall version: 0.3.1

Added#

• Added support for caching Debian apt artifacts.
• Added disable_cache option to disable artifact caching on a per-registry basis.
• Added support for caching responses from the GitHub REST API on GitHub.com and GitHub Enterprise Server (GHES). This includes metadata endpoints, SHA-addressed git objects and source archives, and release-asset and Actions artifact downloads served via signed-blob redirects.
• Added HMAC signing of /redirectz URL matrix parameters, emitted as an additional ;sig=... matrix parameter. Enable via virtual_registry.redirects.signing.enabled; the signing key is read from the environment variable named in virtual_registry.redirects.signing.key_env.
• Added option to disable the /redirectz endpoint entirely through virtual_registry.redirects.enabled.
• Added Varnish Enterprise license reload when supervisor is reloaded via SIGHUP
• Bumped Artifact Firewall to 0.3.0, which adds Maven support, per-version artifact preflight blocking, ruleset persistent storage, and the ability to disable rules at runtime via the admin API. The Supervisor continues to run the firewall in integrated deployment mode behind Virtual Registry, and now registers manifest transformers for the NuGet and Maven ecosystems in addition to npm and PyPI.
• Added top-level otel.endpoint configuration that sets OTEL_EXPORTER_OTLP_ENDPOINT, used by all signals when no signal-specific endpoint is configured. The OTLP SDK auto-appends /v1/<signal> for HTTP protocols.

Fixed#

• Fixed default configuration values being silently lost when a user-provided YAML file set only a subset of fields in the same section.
• Fixed Artifact Firewall returning 503 when firewall.address was omitted from config.
• Fixed fsnotify on user-provided certificates so that they are reloaded when files change on disk.

Virtual Registry 0.10.0 #

Released: 2026-05-11

Varnish version: 6.0.17r3

Artifact Firewall version: 0.2.2

Added#

• Added new Virtual Registry option cache_req_body_limit to set the maximum request body size to buffer for cacheable POSTs (e.g. git-upload-pack).
• Added Git URL cache key normalization. The URL part of Git cache keys is now lowercased and .git extension agnostic.
• Added Git request body cache key normalization. For small request bodies (<10k), agent and session-id telemetry attributes are excluded from the cache key.

Changed#

• Increased default request body buffer size for cacheable POSTs (e.g. git-upload-pack) from 1MB to 10MB.

Fixed#

• Fixed an issue where large Git v2 POST requests would exhaust workspace and fail the transaction.
• Fixed git repository name parsing bug.

Virtual Registry 0.9.0 #

Released: 2026-04-21

Varnish version: 6.0.16r13

Added#

• Added Supervisor packages and Orca Docker image for arm64.
• Added support for caching Git LFS objects. This includes rewriting LFS batch API download URLs to route through the Virtual Registry, where objects are cached as immutable content-addressed downloads.
• Added support for caching PHP/Composer artifacts. This includes rewriting absolute URLs in Composer manifests with the Virtual Registry base_url, enabling caching of both dist archive downloads and source repository clones.
• Added more known OCI User-Agents for pattern matching.

Changed#

• URL rewrites now use matrix parameters to convey extra information about the rewritten URL. This leads to better classification and cache policy for requests to the /redirectz endpoint.
• Caching of HEAD requests from OCI clients is re-enabled. The HEAD requests are not transparently converted to GET requests, opting instead to preserve the request method and cache it separately. This works around the issue of Docker registries that give different response status for HEAD and GET requests.
• For OCI requests, increased cache TTL for the /v2/ ping endpoint to 60s.
• Unsuccessful HEAD preflight requests are now restarted with GET to be able to serve a response body. Like the initial preflight request, the client Authorization header is added to the cache key of the restarted GET request.
• The preflight request for OCI manifests is now re-used by OCI blobs. This means that a single preflight request now authorizes a user for an entire image, instead of needing two.

Fixed#

• Fixed an issue where a license would be considered invalid when the no_restart or shutdown date were set and did not match the expiry date.

Removed#

• Stopped building new packages for Debian Bullseye and RHEL 8. There are no arm64 Varnish packages available for these distributions, and no customers currently relying on them.

Virtual Registry 0.8.3 #

Released: 2026-04-13

Varnish version: 6.0.16r13

Added#

• Added varnish-supervisor packages for Debian Trixie
• Added varnish-supervisor packages for RHEL 10

Fixed#

• Fixed an issue where interrupting the supervisor during VCL loading would hang for 30 seconds before exiting.

Virtual Registry 0.8.2 #

Released: 2026-03-23

Varnish version: 6.0.16r13

Added#

• Added --validate flag which validates the config and exits.
• Added stricter config validation.

Fixed#

• Fixed missing support for custom CA server URLs.
• Fixed an issue where some parts of the configuration would ignore unknown fields instead of exiting with an error.
• Fixed an issue where NPM clients would revalidate their local manifest cache instead of using the new one sent by the Artifact Firewall.

Virtual Registry 0.8.1 #

Released: 2026-03-12

Varnish version: 6.0.16r13

Added#

• Added preparations for Artifact Firewall becoming generally available.

Changed#

• Setting base_url to either http:// or https:// without a domain now determines the scheme of client redirects. This is useful for deployments where the Virtual Registry is deployed behind a TLS terminating proxy, especially when preserve_subdomain is used for the Virtual Registry remotes.

Virtual Registry 0.8.0 #

Released: 2026-03-05

Varnish version: 6.0.16r12

Added#

• Added Cluster option (premium).
• Added dns_ttl option to remotes. This can be used to override the DNS resolution interval indicated by DNS records.
• Added routes option to virtual registries. A route is a glob pattern (fnmatch) that enables more flexible registry routing, where only subdomain-based routing was available before. The subdomain routing still has the highest order of precedence, with routes being matched against the Host header in order of appearance.
• Added preserve_subdomain option to remotes. When used, the incoming subdomain (final component) is appended to the remote Host header when fetching from the remote. The final hostname is also used for DNS and TLS SNI.
• Added readonly option to virtual registries. When enabled, all uploads to the virtual registry are blocked.
• Added extended support for Conan artifacts.
• Added support for caching Ansible artifacts (roles and collections). This includes rewriting the download_url in manifests with the Virtual Registry base_url.
• Added extended support for PyPi manifests. This includes rewriting absolute manifest URLs with the Virtual Registry base_url.
• Added preserve_manifest option to virtual registries. When enabled, base_url insertion into manifests is disabled.

Fixed#

• Fixed subdomain not being parsed correctly for single component Host headers with port.
• Fixed parsing of Docker distribution protocol requests not separating query parameter from manifests referenced by SHA, leading to the being marked as “must-revalidate” instead of “immutable”.
• Fixed Git v2 protocol ls-refs commands not being assigned a “resource_manifest” cache key.

Virtual Registry 0.7.1 #

Released: 2026-02-27

Varnish version: 6.0.16r12

Fixed#

• Fixed an issue where some OCI uploads with Docker clients would fail due to an absolute POST redirect being rewritten with a different prefix than the initial challenge. This caused the Docker client to omit the Authorization header on subsequent PATCH requests, resulting in the upload being aborted with a 401 response. Absolute redirects from the registry are now rewritten as relative redirects.
• Fixed an issue where some base_url rewrites would not restore the original Host header on fetch to the remote.

Virtual Registry 0.7.0 #

Released: 2026-02-23

Varnish version: 6.0.16r10

Added#

• Added OTEL logs support via the otel.logs configuration block. Logs are exported to a configurable OTLP endpoint and do not require a license.

• Added configurable trace sampling via the otel.tracing.sampler configuration option. Supported samplers: always_on, always_off, traceidratio, parentbased_always_on, parentbased_always_off, parentbased_traceidratio. Ratio-based samplers accept an otel.tracing.sampler_arg value between 0.0 and 1.0.

• Added a cache invalidation yKeys for resource types. All objects now get a resource_manifest, resource_package or resource_other key.

• Added base_url option to the virtual registry configuration. This is used whenever the proxy needs to rewrite a response header or body to direct the client back to the virtual registry.

• Added policy for proxying JFrog UI.

• Added dns_ttl option to remotes. When set, this option overrides the DNS resolution interval for the remote, ignoring DNS record TTLs.

Changed#

• Upgraded varnish-otel to v2.2.0, which adds trace sampling and OTEL logs support.

• Remote endpoints are now resolved preemptively in vcl_backend_fetch using utils.resolve_backend(). The Host header is explicitly set based on the remote URL Host. This should not produce a noticeable change.

• Improved cache policy for NPM traffic. All /-/ endpoints are now marked uncacheable. Manifests are now always marked as must-revalidate, meaning they are not cached, but coalesced and candidates for 304 revalidation and stale-if-error.

• Added stricter checking for undefined configuration options. This should make it easier to catch typos in the YAML config.

• The WWW-Authenticate response header is now transparently rewritten when it directs the client to a different domain than the effective base_url. The original URL is preserved and used when the client comes back to authenticate. This enables auth when the upstream registry is not directly accessible by the client.

• For 202 Created responses, the Location header is also rewritten in the same fashion as WWW-Authenticate. This enables OCI uploads when the upstream registry is not directly accessible by the client.

Fixed#

• Fixed varnish-otel failing to find Varnish shared memory when workdir is not explicitly configured.

• Fixed retrying requests when the load balancer has no remaining healthy and unused backends available.

• Fixed a beresp.ttl + req.ttl interaction that resulted in objects marked as must-revalidate not being considered for 304 revalidation and stale-if-error.

• Fixed an issue where OCI uploads would fail with a 404 because the registry returns different responses for HEAD and GET. HEAD requests from OCI clients are now proxied through without a lookup in cache.

• Fixed IPv6 client IPs not being considered local for cache invalidation access.

Virtual Registry 0.6.3 #

Released: 2025-12-17

Varnish version: 6.0.16r8

Fixed#

• Loosen Varnish version license restrictions to ease installation from deb and rpm packages when a new version of varnish-plus is released. Each varnish-supervisor release targets a specific minimum version of Varnish, but it should be possible to use a newer version of varnish-plus than the minimum version.

Virtual Registry 0.6.2 #

Released: 2025-12-01

Varnish version: 6.0.16r7

Fixed#

• Fixed a syntax error in the VCL.

Virtual Registry 0.6.1 #

Released: 2025-12-01

Varnish version: 6.0.16r7

Fixed#

• Fixed the version for the embedded Virtual Registry license.

Virtual Registry 0.6.0 #

Released: 2025-11-27

Varnish version: 6.0.16r7

Added#

• Added support for persisted storage categories.
• Added optional book_size to tune the size of persisted storage books.
• Added default_ttl, default_grace, and default_keep options for Virtual Registries to override the global varnish.params with the same name. Like the global params, these only apply to responses that don’t have an explicit cache policy or Cache-Control header from the remote registry.

Changed#

• The configuration format for varnish.storage has changed. While this technically a breaking change, it’s a licensed feature that has not been put in production anywhere yet. We saw this as an opportunity to do some final polish on the config format without introducing a real breaking change.
• When possible, requests for package manifests are now coalesced when multiple clients request the same manifest at the same time. This can reduce repeat requests to the remote registry while always keeping the manifests fresh.
• Artifacts classified as “other” no longer share a cache namespace with artifacts classified with a specific package type. This resulted in inconsistent cache policies being applied to certain objects, giving them a longer than intended lifetime.
• Registries now have separate cache namespaces. This eliminates potential issues with staging/production setups where repositories and packages have the same name but different manifests. Objects with an immutable cache policy still share a global namespace, so cross-registry Docker layer caching will continue tow work as normal.
• Introduced Stale-If-Error for all cacheable objects, delivering stale objects in case the remote registry is unreachable or produces 5xx responses. Access control for private repositories is still maintained, relying on cached per-user, per-artifact authorization for access control.

Fixed#

• Metrics export now works properly without a license.
• Several issues fixed in the varnish.storage subsystem. The MSE configuration should now be changed to reflect changes in the storage configuration in all cases.

Virtual Registry 0.5.0 #

Released: 2025-11-14

Varnish version: 6.0.16r6

Added#

• Improved cache policy for PyPi. *.whl, *.tar.gz, and *.zip objects are now cached indefinitely while */simple/* is explicitly treated as uncacheable.

Fixed#

• Files under /etc/varnish now has the correct varnish owner in Docker.
• Cache invalidation yKeys for registry name and package type are now created properly.
• Private repositories are no longer treated as public when the private repository caching feature is disabled. Private repository traffic is now passed through the proxy transparently. Does not apply to public OCI repositories, they maintain the previous behavior due to the Authorization header being required.
• Improved cache policy for Maven. Most objects are now cached indefinitely while maven-metadata.xml is explicitly treated as uncacheable.

Virtual Registry 0.4.0 #

Released: 2025-11-04

Varnish version: 6.0.16r4

Added#

• Initial release.