Promote v0.1.67 to main #123
Loading…
Reference in a new issue
No description provided.
Delete branch "trunk"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Every authorize request naming binjovi.repository.create answered {"error":"invalid_request"}, so create_repository could never be used even with the scope on the client and the permission in the control plane policy. Binjovi.MCPOAuth.Protocol builds @scopes at COMPILE time from Binjovi.Domain.MCPPermissions.scopes(), and refuses any request naming a scope outside it. This Deployment was pinned to sha-833fc189660f, which predates create_repository: that revision has no occurrence of the tool at all. So the control plane advertised a tool whose scope this service would never grant. Measured, not guessed. The same authorize request was replayed against the live endpoint twice: without the scope it answers 302, with it 400. Bumped to sha-57d0ab2ab4be, the revision the control plane runs. The two images are pinned in different repositories and nothing keeps them in step; the comment says so, and says to bump this when a new MCP tool ships. Claude-Session: https://claude.ai/code/session_01JGe4pyhQ36AhgDfPJry4d3