All checks were successful
CI / lint (push) Successful in 41s
CI / notebooks-smoke (push) Successful in 1m56s
Deploy / changes (push) Successful in 16s
CI / test (push) Successful in 3m26s
Deploy / zotero (push) Has been skipped
Deploy / docs (push) Has been skipped
Deploy / api (push) Has been skipped
Deploy / bcda (push) Has been skipped
Deploy / llm (push) Has been skipped
Deploy / mc (push) Has been skipped
Deploy / notebooks (push) Successful in 5m14s
Deploy / report (push) Successful in 16s
The 10-27 fix made Renovate process the repo, and a manual run proved it: it opened 2 PRs and a Dependency Dashboard (#1396). But most lookups failed on the anonymous api.github.com limit, it was capped at 2 new branches an hour, and its PRs could never merge, because main still required Woodpecker checks that stopped reporting when CI moved to Gitea Actions. (Fixed in the Gitea branch protection: the CI lint/test/ notebooks-smoke push checks are now the required ones.) - automergeType=branch: once CI is green, minor/patch updates fast-forward onto main as plain commits, with no PRs, matching the main-only workflow. Majors still open PRs for review; automergeStrategy=fast-forward keeps any PR merge free of merge commits. - prHourlyLimit 0; the workflow runs daily, because branch automerge lands on the run after CI goes green. - GITHUB_COM_TOKEN passed to Renovate (secret still to be added). - Leave marimo to marimo_latest.py, hold duckdb <2 like the pyproject cap, and skip the vendored traefik plugin source. - marimo_latest.py fast-forwards the checkout when Renovate has moved the server's main, instead of aborting.