Some checks failed
CI / lint (push) Successful in 33s
CI / test (push) Has been cancelled
CI / notebooks-smoke (push) Has been cancelled
Deploy / changes (push) Has been cancelled
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 16s
Infra CI / docs (push) Successful in 21s
Infra CI / notebooks (push) Successful in 51s
Infra CI / api (push) Successful in 14s
Infra CI / bcda (push) Successful in 15s
Infra CI / llm (push) Successful in 20s
Infra CI / mc (push) Successful in 17s
Renovate on Gitea refuses github-tags/-releases lookups without a
GITHUB_COM_TOKEN ("GitHub token is required for some dependencies"),
which left yq, otel-cli, trivy and crane untracked. Each publishes a
versioned image, so their pins now use datasource=docker (tags verified
for the current versions: mikefarah/yq, ghcr.io/equinix-labs/otel-cli,
aquasec/trivy, gcr.io/go-containerregistry/crane).
The github-actions block meant to limit that manager to renovate.yml
never did: managerFilePatterns adds to the defaults, so every generated
workflow was scanned too. Drop it; a packageRule disables github-tags
action pins (token-only, and gen_config.py owns those files) while
Renovate's own container image stays tracked. requires-python is a
floor, not a dependency, so the pep621 python lookup is off.