fix(apps): re-consent on new destructive jobs and weaker endpoints; external Node logic publishes
Radin committed
- Author
- Radin · radin@coline.appOct 1, 2026 at 05:52
- Committer
- Radin · radin@coline.appOct 1, 2026 at 05:52
- Parents
- 20a94d43a324
fix(apps): re-consent on new destructive jobs and weaker endpoints; external Node logic publishes From a Sol (GPT-6.1) review of the SDK and CLI, each reproduced: - A new job exceeding anything the app could previously do (tools or jobs) now requires re-consent; only renamed-in-place jobs were checked, so an update could add a destructive job and auto-update silently. - An existing endpoint that drops verification, or accepts more methods, requires re-consent (endpoints were compared by id only). - A connection whose authorizeUrl or tokenUrl changes requires re-consent: the token URL receives authorization codes. - check/push bundled app.config.ts for the browser even when every handler runs on the developer's server, so an external app importing Node code (a database, files) could not publish. Such apps now read their manifest from a Node build (SDK bundled, other dependencies left as imports) and upload no logic bundle; hosted logic that imports Node modules fails with an explanation instead of a bare resolve error. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1 file changed+33−1