You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
bug(safe-inputs): script: return value is silently dropped — execute() never called at runtime #18534
Safe-input tools using inline script: with return always return {"stdout":"","stderr":""}. The documentation shows returning objects from scripts, but the return value is silently dropped.
Root cause
The compiler (generateSafeInputJavaScriptToolScript in pkg/workflow/safe_inputs_generator.go:181) correctly wraps the user's script in an async function execute(inputs) and exports it via module.exports = { execute }. This supports return as documented.
However, the runtime (createJavaScriptHandler in actions/setup/js/mcp_handler_javascript.cjs) executes the generated .cjs file as a standalone Node.js process via execFile and reads stdout for the result. It never require()s the module or calls execute(). The process defines the function, exports it, and exits with empty stdout.
Activity
Add fork context warning to validate_secrets.cjs (github#18523)
pelikhan commentedon Feb 27, 2026
@copilot change the wrapping so that it designed to run as a node file.