Closed
[WIP] Register safe output MCP server as Node.js runtime#5942
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix safe-outputs MCP server runtime mode and bundling
Problem
The safe-outputs MCP server JavaScript is executed as a standalone Node.js process but:
RuntimeModeGitHubScriptinstead ofRuntimeModeNodeJS/// <reference types="@actions/github-script" />TypeScript referencePlan
safe_outputs_mcp_server.cjsRuntimeModeGitHubScripttoRuntimeModeNodeJSGetSafeOutputsMCPServerScriptto useRuntimeModeNodeJSmake agent-finishfor final validationOriginal prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.