Mauricio Siu 6239073e2a fix: strip git provider secrets from compose.one response ... findComposeById embedded the full github/gitlab/bitbucket/gitea relations (client secrets, OAuth tokens, private keys, app passwords) and compose.one only used canEditDeployGitSource to set a hasGitProviderAccess flag, never to hide the fields — so any member with read access to a compose service got the connected git provider's raw credentials, regardless of their access to that provider itself. Exclude the same secret columns findApplicationById already excludes. Deploys are unaffected: the actual clone step always re-fetches the provider fresh by id (findGithubById/findGitlabById/...), it never reads secrets off the embedded relation.		2026-09-01 03:24:43 -06:00
..
server	fix: strip git provider secrets from compose.one response	2026-09-01 03:24:43 -06:00