v0.8.52: org and perm group cli endpoints, upgrade trigger

[waleedlatif1]

• feat(organizations): expose organization and permission group administration (feat(organizations): expose organization and permission group administration #8102)
• chore(ci): give the Trigger.dev upload job room for a slow image push (chore(ci): give the Trigger.dev upload job room for a slow image push #8115)
• chore(trigger): upgrade Trigger.dev to 4.5.16 so deploy images build without deleting node_modules (chore(trigger): upgrade Trigger.dev to 4.5.16 so deploy images build without deleting node_modules #8118)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
docs	Ready	Preview	Sep 21, 2026 9:03pm UTC

[greptile-apps]

Confidence Score: 4/5

The PR appears safe to merge after correcting the non-blocking audit attribution for multi-workspace invitation resends.

Findings

1.  Audit uses wrong workspace ▶

Summary

This PR adds public v2 organization and permission-group administration, projects those APIs into the CLI, MCP, OpenAPI, and documentation surfaces, consolidates internal organization operations behind shared application use cases, strengthens invitation mutation consistency, and upgrades Trigger.dev.

• Adds organization, member, workspace, invitation, and permission-group API operations.
• Adds generated CLI commands, MCP mappings, OpenAPI resources, and command documentation.
• Refactors authorization, locking, auditing, and membership cleanup into shared application boundaries.
• Preserves deployment ordering while aligning Trigger.dev packages and CLI at 4.5.16.
• One audit-attribution issue remains for multi-workspace invitation resends.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  Client[CLI / MCP / API client] --> Contract[v2 route contract]
  Contract --> Auth[Credential and organization authorization]
  Auth --> UseCase[Shared application use case]
  UseCase --> Domain[Organization / invitation / permission-group manager]
  Domain --> DB[(Database)]
  UseCase --> Audit[Semantic audit trail]
  Contract --> Presenter[Validated response presenter]
  Presenter --> Client

Loading

_{Reviews (1) · Last reviewed commit: "chore(trigger): upgrade Trigger.dev to 4..."}

[greptile-apps]

Audit uses wrong workspace

For a multi-workspace invitation, resend authorization can succeed through any grant the actor administers, but this audit entry always uses the first grant. If the actor administers a later grant instead, the action is recorded against a workspace where they may have no administrative authority, making the audit trail misleading. Record the workspace that actually satisfied authorization.

Knowledge Base Used: Identity, authentication, and authorization