Artifact Keeper 1.12.4
1.12.4 is a patch release on 1.12: about 17 fixes and four security fixes, no migrations, no API removals. Upgrade from 1.12.3 directly; from 1.12.2 or earlier, read the 1.12.3 upgrade notes first. The headline fixes are Go @v/list, @latest and .info answering an upstream outage with a 5xx instead of 404 (#6214), uploads that are never answered with an error after they were stored (#6317), Maven age-gate metadata whose checksums match the document served (#6284), a migration worker that stops as soon as it loses its job (#6305), and containerd fixes for CVE-2026-95839 in the backend and scanner adapter images (#6394).
Upgrade notes
Migrations
None. 1.12.4 adds no database migration, so rolling back to 1.12.3 needs no SKIP_MIGRATIONS and no manual step.
Behaviour changes operators will notice
- Go: an upstream outage is now a 5xx, not a missing module (#6214). When a Go Remote cannot reach its upstream, or the upstream answers 5xx or 429,
@v/list,@latestand.infonow answer502or503, as.modand.zipalready did, and a Virtual answers503withRetry-Afterwhen no member served and one could not answer. A server-side fault while resolving them (for example a database pool timeout) is a 5xx too. The same applies when the upstream answers401/403to a Remote that has upstream credentials (expired or revoked ones, set as upstream auth or embedded in the upstream URL asuser:pass@):502on the Remote, or503through a Virtual, where.modand.zipalso changed from404to503for a member refusing its own credentials.gotreats a404as "this proxy does not have the module" and moves to the nextGOPROXYentry, but stops on a 5xx. So withGOPROXY=<ak>,direct, a build during an upstream outage now fails with the 5xx instead of fetching directly from VCS past the scan gate, and with a singleGOPROXYentry it fails with a 5xx instead of a not-found error. If you relied on thedirectfallback during outages, useGOPROXY=<ak>|direct(fall through on any error) knowing that it skips scan-on-proxy, or wait for the upstream. A module the upstream does not have (404/410) still answers404, and so does a refusal of a Remote with no upstream credentials. - A Remote or Virtual npm repository answers
npm whoamiandnpm pingitself (#5634).whoamireturns the Artifact Keeper username (or401without credentials) instead of forwarding to the upstream;pinganswers200 {}with no upstream round trip. - The generic
PUT /api/v1/repositories/{key}/artifacts/{path}answers201once the artifact is stored (#6317), even when a read that only fills the response fails afterwards; that field then readsdownload_count: 0or has no revision, and a warning is logged. PyPI and Debian metadata now commit with the artifact row, so a failed upload stores nothing and its retry succeeds instead of getting409. - Maven age gate: metadata responses carry
X-Checksum-SHA1andX-Checksum-MD5of the served body and are servedCache-Control: no-cachewhile versions are still being dated (#6284). The fix is per backend process: with several replicas, clients that fetch checksum files as separate requests (coursier, Ivy, strict Maven 3.8) can still see a mismatch while a GA is being dated, so use sticky sessions for them. versioning_enabled: trueon a format that does not version uploads returns aWarning: 299header on repository create and update (#6063). The request still succeeds and the value is still stored.- PyPI: a proxy
502carriesX-AK-Upstream-Statuswith the upstream's status, and PEP 691 negotiation honoursqvalues (#5643). A client that ranks HTML above JSON now gets HTML; pip and uv are unaffected. POST /api/v1/quarantine/{id}/releaseaccepts an optionalexpected_digest(#5766). With it, a release decided for one image no longer clears a hold placed on the image a tag has since moved to. Requests without a body behave as before.- Composer
search.jsonon a Virtual returns its Local and Staging members' packages, one hit per name, andper_pageis clamped to 1–100 (#6285). - A migration worker that loses its claim stops at once and no longer writes the final status over a run that took the job over (#6305).
New and changed settings
ADVISORY_EXCLUDE_PATTERNS(new, unset: no change) keeps matching packages out of OSV.dev and GitHub Advisory Database lookups (#5691). It takes comma-separated package-URL globs such aspkg:maven/com.example.internal/*,pkg:npm/@acme/*. Matching packages stay in the inventory and SBOM and are still matched by grype and trivy. Patterns withoutpkg:, with a version or with qualifiers match nothing and are logged as a warning at startup.docker-compose.ymlforwardsLDAP_BASIC_AUTH_PASSTHROUGH(#6160), stillfalseby default. Setting it in.envnow reaches the backend container.- Scanner adapter 1.7.2 (#6394) is a separate image. It bundles trivy 0.76.0 rebuilt against containerd v2.4.2 and still pairs with the 0.76.0 trivy server sidecar. Installs that pin the adapter to an exact version should move to
1.7.2; the floating:1tag picks it up.
Security
- CVE-2026-95839 (containerd): the backend image's bundled
buildctlnow links containerd v2.3.7 (BuildKit stays at v0.33.1), and the scanner adapter's bundled trivy links containerd v2.4.2, shipped as scanner adapter 1.7.2 (#6394). Both binaries are clients and do not run the containerd daemon the advisory describes; the update clears the image scans. - wasmtime and wasmtime-wasi 36.0.22 for RUSTSEC-2026-0587, a WASI filesystem sandbox escape on Windows (#6356). The plugin runtime preopens no directories, so no known path reaches it.
ADVISORY_EXCLUDE_PATTERNSlets you keep internal package names out of third-party advisory lookups (#5691).- An OCI release and the scanner's
flaggedmark are bound to the digest they were decided on (#5766).
Formats, proxy and storage
- Go:
@v/list,@latestand.infoanswer an upstream outage or a rejected upstream credential with a 5xx (#6214). - Maven: age-gated
maven-metadata.xmland its checksums describe the same document (#6284); uploads with LDAP credentials work with the shipped compose stack, and a directory user naming an unknown repository gets the same404as any valid credential (#6160). - npm:
whoamiandpingare answered locally on every repository type (#5634); a deletedyarn,pnpmorbowerversion leaves the Virtual packument and dist-tags straight away (#5779). - NuGet: packages uploaded through the web UI are indexed as packages (#6062).
- PyPI: upstream status on a proxy
502,q-aware PEP 691 negotiation, andrepo_selectoron the user token routes (#5643); PyPI and Debian metadata commit with the artifact row (#6317). - Composer:
search.jsonon a Virtual searches its members (#6285). - Repositories:
versioning_enabledon a format that ignores it is flagged with aWarningheader (#6063).
Scanning, migration and operations
- SBOM license expressions survive when the Trivy filesystem scanner also catalogued the package (#5629).
- A migration worker that loses its claim stops at once (#6305); startup migrations no longer leave long statement and lock timeouts on an application pool connection (#6319).
- A restore that deadlocks on the usage ledger is retried (#5084).
- A failed Remote MCP sync pass is recorded before its lock is released, and the sync status reads the lock first (#6249, #6388).
- Development and CI: steadier release pipeline (macOS build time, the release commit kept a branch tip until its Release exists, read-only and sha-pinned binary builds) and test suite (#6218, #6338, #6381, #6329, #6252).
Sponsors
Thank you to our sponsors for supporting ongoing development of Artifact Keeper.
Backers
- Advailo, SIA (@advailo)
- Ash A. (@dragonpaw)
- Mike (@huylv95)
- Gabriel Rodriguez (@injectedfusion)
- Narek Engibaryan (@narek01)
- and one sponsor who chose to stay private
Become a sponsor to support the project and get your name listed here.
Thank You
Thanks to the external contributors and issue reporters who shaped this release.
Contributed code
- @macmoonshine: NuGet packages uploaded through the web UI indexed as packages (#6268), Maven uploads with LDAP credentials (#6262), and startup migration timeouts no longer leaking into the application pool (#6348).
- @nicola-preda: retries for the release pipeline's CLI cache warm-up dispatch (#6204), and co-author of the Maven age-gate checksum fix (#6328, from #6342) and the LDAP upload fix (#6262).
Reported the issues this release closes
- @cervotoc: Maven age-gate metadata and its checksums disagreeing (#6284) and Composer
search.jsonon a Virtual answering nothing (#6285). - @romainwager: Go
@v/list,@latestand.infoanswering404during an upstream outage (#6214). - @matthiasmast: keeping internal package names out of external advisory lookups (#5691).
- @major-sam: NuGet uploads through the web UI creating no package (#6062).
- @lalten:
versioning_enabledaccepted for formats that ignore it (#6063). - @bgp-sz: Maven uploads failing for LDAP users (#6160).
Full changelog: v1.12.3...v1.12.4