Skip to content

Route every Maven artifact file through the download path - #556

Merged
andrew merged 1 commit into
git-pkgs:mainfrom
simonchrz:fix/maven-extensions
Oct 23, 2026
Merged

andrew merged 1 commit into
git-pkgs:mainfrom
simonchrz:fix/maven-extensions

Conversation

@simonchrz

Copy link
Copy Markdown
Contributor

Only Maven files with a known artifact or checksum extension went through the download path. Others, such as the .exe binaries protoc and gRPC plugins publish, or .hpi and .so files, were relayed as is and skipped the denylist, cooldown, scanning and the cache.

Any file in a version directory named {artifact}-{version}... (timestamped for SNAPSHOTs) now takes the download path. Directory listings and catalogs are still proxied, and cache keys for the existing extensions don't change.

Only files with a known artifact or checksum extension went through the
download path; anything else, such as the .exe binaries protoc and gRPC
plugins publish or .hpi and .so files, was relayed from upstream as is.
Those files skipped the denylist, cooldown, scanning and the cache. Any
file in a version directory named {artifact}-{version}..., the way Maven
names what it publishes (timestamped for SNAPSHOTs), now takes the
download path. Directory listings and catalogs are still proxied.
@andrew
andrew merged commit 6b36f59 into git-pkgs:main Oct 23, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants