Files
Ruben Fiszel 751c999e26 fix: read every colon split in a builder app's triggerable keys
`execute_component` looks up `format!("{component}:{path}")` and `component` is an
unrestricted string, so every colon in a triggerable key is a possible split, not
just the first. Validation stripped only up to the first one, so `x:y:script/hub/1/foo`
parsed as neither a script nor a flow key and was skipped entirely, while a request
with `component = "x:y"` matched it exactly. A builder could deploy a clean
Publisher app and run hub code, or any unreadable runnable, on a worker.

Now every suffix that parses as a runnable is validated, rather than guessing which
one a request will use.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-17 16:49:46 +00:00
..