connectors 0.4.1
Added
- Add governed outbound MCP as a generated Connector service. A reviewed profile freezes the full
remote tool snapshot and assigns local operation identity, prose, and effect; the ordinary
deployment overlay still owns exposure, risk, approval, grants, endpoint and credential
bindings. HTTP exchanges stay inside Connection-bound egress and fetch bearer material from the
Connector secret store per exchange. - Add a generator-facing service factory contract and deterministic runtime bundle builder. A
registered factory remains inert until an explicit deployment overlay assigns permanent provider
identity and complete operation policy/resource bindings; provider and operation collisions,
incomplete overlays, and catalog/dispatch drift refuse composition. - Activate generated service bundles as ordinary hosted backends with exact durable Grants,
explicit operation admission, and readiness reporting for every composed service. - Add bounded, single-use human approval evidence bound to the authenticated subject, exact
operation, Connection, description lease, canonical input, and a five-minute maximum lifetime. - Route hosted GitLab OAuth, PAT verification, project discovery, repository reads, and operation
dispatch through the exact-origin Connection-bound post-DNS transport.
Changed
- Carry the optional realm only in receiver-verified principal context. It is absent from service
operation coordinates, and an absent realm remains distinct from the literal realmdefault.
Security
- Refuse hosted GitLab unless
connection_bound_post_dns_v1is declared, and include GitLab in the
exhaustive source fence that rejects raw HTTP clients, DNS resolution, and outbound sockets from
credential-bearing Integration adapters.
What's Changed
- feat: expose governed GitLab repository context by @b10x-bot[bot] in #1
- gitlab: confine hosted provider egress by @b10x-bot[bot] in #2
New Contributors
- @b10x-bot[bot] made their first contribution in #1
Full Changelog: v0.4.0...v0.4.1