Repository navigation
v0.2.3 (2026-11-16)
This release is published under the MIT License.
Bug Fixes
- http: Build every HTTP client through provider.http_client (
e62eeb5)
Provider._http and read_protected_resource_metadata each built their own httpx2.Client, spelling the timeout, the User-Agent header and follow_redirects=False twice. A setting added to one (a retry, a proxy, a different timeout) would have reached the OAuth exchanges and not the RFC 9728 metadata lookup, or the reverse.
provider.http_client(user_agent) now builds the client once, both call sites use it, and CLAUDE.md names it as the one door for HTTP requests. A Provider handed a client still uses that one.
Agent-Name: inbox.problem.fix
Agent-Session: 01a1e20e-7649-7c2d-9c8d-ae2f4aeabe7a
Agent-Run: 01a1e20c-a4fe-7736-a487-c6ac04b27c92
- product: Decide which credential applies in one place (
7f50557)
Four sites decided which of the three credential sources applies, in two orders. token_source and repair checked the file's token_command first; the status command and the logout refusal checked the service secret first. With both set, every API request refused two credentials while auth status reported a service client, and logout refused as a service.
Product.credential returns a Credential (COMMAND, SERVICE, PERSON) in token_source's order and raises ConfigRefused on two credentials. token_source, repair, the status dispatch and the logout refusal all match on it, so status and logout now give the same two-credentials refusal every request gives. Credential is exported. A test pins the refusal on the classifier.
Agent-Name: inbox.problem.fix
Agent-Session: 01a1e20e-7649-7c2d-9c8d-ae2f4aeabe7a
Agent-Run: 01a1e20c-a4fe-7736-a487-c6ac04b27c92
- product: Name the auth command group once, on Product (
e34b8be)
add_auth_commands took the group's name as a parameter, yet Product.login_command and both NotConfigured refusals in deployment.py each hard-coded 'auth login'. A CLI registering its group under another name was told to run a command it does not have: by the not-logged-in hint, by status, and by every not-configured refusal.
AUTH_GROUP in deployment.py is the default, Product.auth_group carries a CLI's choice, and login_command builds from it. add_auth_commands defaults its group name to product.auth_group, and load_deployment and deployment_for_login take the login command from their caller, which Product passes. The default text is unchanged.
Agent-Name: inbox.problem.fix
Agent-Session: 01a1e20e-7649-7c2d-9c8d-ae2f4aeabe7a
Agent-Run: 01a1e20c-a4fe-7736-a487-c6ac04b27c92
- status: Open every status report with one set of deployment fields (
2ca3111)
The person, service and handed-token status reports each rebuilt config_file, api and client_id from the deployment as their own dict, and the service report read client_id and issuer back from the provider it had just built from the same deployment. A field added to where the CLI is pointed had to be added three times, and the handed-token report already lacked issuer.
pointed_at(resolved) builds config_file, api, client_id and issuer once, and each report adds only its own verdict fields to it. The handed-token report's --json now carries issuer too; no key any report printed is removed.
Agent-Name: inbox.problem.fix
Agent-Session: 01a1e20e-7649-7c2d-9c8d-ae2f4aeabe7a
Agent-Run: 01a1e20c-a4fe-7736-a487-c6ac04b27c92
Chores
- ci: Regenerate the hooks and CI at toolchain stamp 61 (
0012b99)
env FORGE_REPOS_REGISTRY=$FLEET_LIBRARY_DIR/repos.json FORGE_VERSIONS_FILE=$FLEET_LIBRARY_DIR/pinned-versions.json forge repos apply --yes wrote this in fleet's repos-toolchain-rollout job, and fleet committed it through the repo's hooks.
Agent-Run: 01a1dc27-58a0-769a-a17f-e1c04742e9d2
Detailed Changes: v0.2.2...v0.2.3