Remove inline safe-outputs MCP server entry point generation - files now installed by action #7486
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.
The safe-outputs MCP server entry point is now deployed as a static file through the
setup-safe-outputsaction instead of being generated inline in each workflow.Changes
1. Created Static Entry Point File
pkg/workflow/js/safe_outputs_mcp_server_entry_point.cjsas a source filepkg/workflow/js.gowith//go:embeddirectiveGetJavaScriptSources()map for build system access2. Updated Action Build Configuration
pkg/cli/actions_build_command.goto include entry point insetup-safe-outputsdependenciesactions/setup-safe-outputs/copy-files.shto renamesafe_outputs_mcp_server_entry_point.cjstomcp-server.cjsduring copy3. Removed Inline Generation
pkg/workflow/mcp_servers.goImpact
Testing
copy-files.shcorrectly renames entry point tomcp-server.cjsOriginal prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.