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.
Compatibility
- Web 1.11.3 is the first 1.11.x web that runs against backend 1.12.0 (#1178, artifact-keeper/artifact-keeper#5663) - Backend 1.12.0 reports a package's
download_countasnullwhen it cannot tie the package to its downloads, which is the case for a Remote or Virtual Maven package cached through a streamed pull-through (artifact-keeper#5419). Web 1.11.2 and earlier format that count without a null check, so against backend 1.12.0/repositories,/packagesand every Remote or Virtual Maven repository page show "Something went wrong". Web 1.11.3 shows a dash for that count or leaves it out (see Fixed). For backend 1.12.0, web 1.12.0 is still the matching release: it carries the UI for the rest of the 1.12.0 changes. Backend 1.11.14 needs web 1.11.3 (or 1.12.0) for TOTP accounts that sign in through LDAP or SSO. On backend 1.12.0, the Security page shows an empty grade badge for a repository the backend reports as unrated (nullgrade); web 1.12.0 has the same gap (#1177).
Fixed
- Package downloads and versions read as the backend reports them, and a rejected file is badged Rejected (#1178, backport of #1085) - A package or version download count that is null, missing or zero shows as a dash, or is left out, instead of "0 downloads" or an error. That keeps the repository pages working against backend 1.12.0 (see Compatibility). A rejected file in a repository's file list was badged "Quarantined"; it is now badged "Rejected", a conda withdrawal "Withdrawn", and a released or expired hold shows no badge. Versions of revision- or tag-style formats (Hugging Face, ML models, Git LFS, generic, the OCI family and container images) show as stored, so a Hugging Face revision reads
maininstead ofvmain, and a Go version that already starts withvis not doubled. Trade-off: since backend 1.12.0 a 0 is a real count, and it is still shown as a dash. - LDAP, OIDC and SAML sign-in asks for the TOTP code on accounts that enrolled one (artifact-keeper#5484) - Backend 1.11.14 and 1.12.0 stop treating a directory password or an IdP assertion as a complete sign-in for an account with TOTP enrolled: LDAP login and the OIDC/SAML code exchange now answer with the same TOTP challenge as the local login, and set no session. This UI did not know that answer, so such a user who signed in through LDAP or SSO was sent back to the login page with no session and no message. The LDAP form and the
/callbackpage now show the existing two-factor form and finish the sign-in atPOST /auth/totp/verify; accounts without TOTP sign in as before. A background silent-SSO check (prompt=none) that meets a TOTP account stays signed out instead of prompting; the user signs in with the SSO button and enters the code then. Run this UI with backend 1.11.14 / 1.12.0 or later for TOTP accounts that use LDAP or SSO; against an older backend nothing changes. - The cargo setup guide gives an index URL cargo can use (#1129, #1130, #1196) - The
~/.cargo/config.tomlstep now setsindex = "sparse+<url>/cargo/<repo>/". The old URL had nosparse+prefix, so cargo treated it as a git index, and it ended in/index, where the backend does not serveconfig.json. - A Maven POM row opens the artifact detail dialog (#1035, #1123, #1197) - In a Maven repository's grouped Artifacts view, the
.pomrow was a plain download link, so the POM was the one file of a component that could not be opened, inspected or deleted from the UI. It now opens the detail dialog like every other file row, keeps its POM badge, and has a separate download button. - Storage totals count the proxy cache once (#1039, #1093, #1198) - The Storage Analytics Total Storage card, the storage trend and the dashboard's Storage Used card added
proxy_storage_bytestototal_storage_bytes, which already includes the proxy cache, so instances with remote repositories showed inflated totals. The totals now usetotal_storage_bytesalone, and the local half of the hover breakdown is the total minus the proxy cache. - The repository Storage card shows the used size until storage stats are computed (#1131, #1169, #1199) - Until the backend's storage stats refresher has visited a repository, its storage endpoint answers zeros with no
computed_at, so the card read "Logical size 0 B" under a header saying the repository used hundreds of megabytes. The card now shows the repository's own used size with a note that the breakdown is not computed yet. A virtual repository shows the size held by its members. - The PyPI Tracks tab shows on local and staging repositories (#1066, #1183, #1200) - The backend accepts PEP 708 tracks declarations only on the local or staging repository that owns the project, but the tab was shown only on virtual PyPI repositories, so every declaration made from it failed. A virtual repository still applies the tracks declared on its local members.
- A fresh load after the access cookie expires stays signed in (#1084, #1125, #1201) - When the UI was opened more than the access token lifetime (30 minutes by default) after the last activity,
/auth/meanswered 401 and the shell rendered as signed out, while the page's data requests refreshed the session on their own. The initial load now refreshes the session once on that 401 and asks again, sharing one in-flight refresh with the request interceptor, and refetches the queries answered as anonymous. - The protobuf setup guide no longer generates buf CLI steps that cannot run (#1064, #1065, #1203) - The guide gave a five-segment
buf.yamlmodule name, which buf rejects, andbuf push --registry, a flag buf does not have. Backend 1.11.x also answers the buf CLI with 415 on hosted repositories. The guide now says the buf CLI is not supported against backend 1.11.x (backend 1.12.0 adds it for local and staging repositories, and web 1.12.0 shows those steps), and gives local and staging repositories the JSON ConnectUploadService/UploadandDownloadService/Downloadcalls instead, which backend 1.11.14 and 1.12.0 both accept. This is a 1.11.x-only change: main's fix gives buf CLI steps that need backend 1.12.0. - The Permissions page lists every permission (#1181, #1182, #1205) - The page asked for 1000 permissions in one request, and the backend caps a page at 100, so only the first 100 rules were listed. The table now pages on the server (20, 50 or 100 a page) and steps back a page when a delete empties the last one.
- A stored record_only proxy scan action is kept (#1069, #1122, #1207) - The repository scan settings showed a stored
record_onlyproxy scan action as fail-open, and saving any scan field rewrote it tofail_open. The action now shows as stored, and a save sends it back unchanged. - Saving the age gate keeps an instance lock that was handed back (#1038, #1126, #1208) - For an instance administrator, the backend treats an age gate save without
instance_lockedas locking the policy, so saving the form re-locked a policy that had been handed back to the repository's administrators. The form now shows the lock state, gives instance administrators a switch, and sends the lock back on their saves, only when the backend reports it. Backend 1.11.14 does not report the lock, so nothing changes there. - Hidden and bidi characters in a repository description are shown visibly (#1107, #1127, #1209) - The repository and staging repository headers rendered the description as stored, so bidi overrides could make a name like
gnp.exeread asexe.png, and zero-width or control characters were invisible. They now show as[U+XXXX], and an over-long description is cut with the whole text in a tooltip. The MCP views main also hardens are not in 1.11.x. - Saving the scan settings keeps an instance lock that was handed back (#1185, #1186, #1216) - For an instance administrator, the backend treats a repository security config save without
instance_lockedas locking the proxy scan policy, so saving any scan field from the Scanning & enforcement settings or the repository Security tab re-locked a policy that had been handed back to the repository's administrators. Both forms now send the lock back unchanged on an instance administrator's save, only when the backend reports it, and the settings show a lock switch. Backend 1.11.14 does not report the lock, so nothing changes there.
Notes
- 1.11.x maintenance line (#1159) - Web 1.11.x patches now come from
release/1.11.x, which runs the same required checks asmainand runs E2E against backend 1.11. A tag gets thelatestimage tag and the Latest Release only when it is the highest stable version, so a 1.11.x patch published after 1.12.0 does not replace 1.12.0 aslatest. - List-page E2E search locators are scoped to the main landmark (#1062, #1184, #1206) - On a first load, React's streamed server copy of a page can sit in a hidden element next to the client-rendered page, so the E2E search locators sometimes matched two inputs. Test-only.
What's Changed
- fix(auth): ask for the TOTP code after LDAP, OIDC and SAML sign-in (artifact-keeper#5484) [1.11.x] by @brandonrc in #1159
- chore(release): web 1.11.3 prep: CHANGELOG section with Sponsors, version bump by @brandonrc in #1160
- fix(packages): show null download counts as a dash, badge rejected files as rejected (#1085) [1.11.x], fold into 1.11.3 by @brandonrc in #1179
- fix: 1.11.3 backports of the 1.12.0 fix wave, fold into 1.11.3 by @brandonrc in #1210
- fix(scan): keep the instance lock when saving scan settings (#1185) [1.11.x], fold into 1.11.3 by @brandonrc in #1218
Full Changelog: v1.11.2...v1.11.3