Some checks failed
CI / lint (push) Successful in 47s
CI / notebooks-smoke (push) Successful in 2m40s
CI / test (push) Has been cancelled
Deploy / changes (push) Has started running
Deploy / notebooks (push) Has been cancelled
Deploy / zotero (push) Has been cancelled
Deploy / docs (push) Has been cancelled
Deploy / api (push) Has been cancelled
Deploy / bcda (push) Has been cancelled
Deploy / llm (push) Has been cancelled
Deploy / mc (push) Has been cancelled
Deploy / report (push) Has been cancelled
Infra CI / zotero (push) Successful in 26s
Infra CI / docs (push) Successful in 42s
Infra CI / notebooks (push) Successful in 1m59s
Infra CI / api (push) Successful in 2m19s
Infra CI / bcda (push) Successful in 3m0s
Infra CI / llm (push) Successful in 1m11s
Infra CI / mc (push) Successful in 1m12s
Package Supply Chain / pkg-supply-chain (push) Successful in 4m9s
publish refuses a bag that does not verify or a version already out, then copies it under data/lead/releases (served read-only by the landing nginx at reach.<domain>/releases/ only, through git-sso like the rest of reach), rewrites index.json/index.html, archives a tarball to rustfs bucket lead-releases via the mc container's rc, creates the Gitea release lead-review-v<version> at the bag's commit, and adds a bib item with the RO-Crate attached. The bags hold the stack's source, so they stay behind SSO until a decision to publish them openly.