Skip to content

librarian v0.20.0

Choose a tag to compare

@github-actions github-actions released this 16 Nov 20:20
· 32 commits to main since this release

The database decides; GitHub is the record

  • Approvals take effect at once. Approving a learned API, enabling writes and every other decision is now a database write, in effect on every replica immediately. There is no pull request to merge and no registry sync to wait for.
  • GitHub receives a commit for every decision and is never asked. Each approved entry and decision is written to the record repository afterwards, in the background and with retries; a failed or slow GitHub never blocks or undoes a decision, and the repository is not read back. librarian registry restore rebuilds a database from it.
  • Updates to a verified API get their own page. When an API changes at its source, approvers get an approve-or-deny page for the update. Any API can be approved or forgotten from the console.
  • The chart no longer needs git-sync for the record (githubApp.repo).

Agents on Agent Substrate and kagent

  • Agents call librarian with no key of their own. Their sandboxes hold no credentials: the platform's egress gateway signs each request with the actor's identity, librarian verifies it against the cluster's issuer, resolves the session to its kagent Agent, and applies the rule for that agent (substrate.rules: which APIs, which writes, who approves). Grants, rate limits and the audit trail follow the agent across its sessions.
  • The chart registers librarian with kagent as a RemoteMCPServer (substrate.enabled), under its fully qualified name, and mounts the cluster signer's trust bundle.
  • Tested end to end on kind (Kubernetes 1.35) with kagent 1.0.1 and Agent Substrate 1.0.0; the steps and manifests are in tests/integration/substrate. Through kagent the person behind an agent is not known, so a rule's owner approves that agent's writes.

Security fixes

  • An API that sends the key back no longer hands it to the agent. Some APIs answer with the request they received: an echo or debugging endpoint, a link that repeats the query string with its key, an error page that quotes the URL, a message that names the rejected key. librarian passed such an answer on, to the calling agent, to the model planning a plain-language request, and into the result stored with a write's approval. The credential a call was sent with is now removed from every answer first (shown as [redacted]): as sent, for Basic authentication also as the encoded pair and its password, and as a URL, a JSON string or an HTML page would write it. A value shorter than six characters is left alone, because replacing it would mangle ordinary data.
  • A stored key that ends with a line break no longer leaks through an error. A key created from a file usually ends with a line break. With such a key in the environment or AWS Secrets Manager store, the HTTP client refused the request with an error that quotes the header it refused. On 0.19.1 that put the read key into librarian's log and, for an approved write, the write key into the agent's answer and the approval's record. Now whitespace around a stored credential is not sent (so such a key simply works), a key with a line break or a non-ASCII character inside it is refused before anything is sent, with a reason that does not name it, and the HTTP client's own message is never passed on.
  • Dependencies: certifi 2026.10.23 (the older CA bundle trusts roots whose intermediate keys were compromised; this is the bundle behind librarian's outbound calls), pyasn1 0.6.5 and opentelemetry-api 1.45.2 (denial-of-service fixes).

After upgrading: results and failure notes stored by earlier versions are not rewritten. If you write to an API that sends its key back, or a write ever failed with "Illegal header value", replace that write key. Logs from earlier versions may hold a read key in the same error.

Upgrade

  • From 0.19 or earlier with a registry repository: upgrade with your values unchanged, so the first start imports the reviewed entries into the database. Check the console lists your APIs, then set githubApp.repo and drop registry.gitSync. Review pull requests librarian left open are closed with a comment saying where the review continues. Details: docs/registry.md.
  • Answers may now contain [redacted] where an API repeated the credential. Nothing else in an answer changes.
  • No other configuration changes. substrate.* is off unless you enable it.