Repository navigation
Make Sentry MCP queries explicit in smoke OTEL workflow - #32185
Merged
Merged
Conversation
Co-authored-by: mnkiefer <8320933+mnkiefer@users.noreply.github.com>
Co-authored-by: mnkiefer <8320933+mnkiefer@users.noreply.github.com>
mnkiefer
approved these changes
May 14, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the Smoke OTEL Backends workflow to launch the Sentry MCP server via an explicit containerized stdio configuration (instead of relying on npx implicit behavior), and regenerates the compiled lock workflow so runtime configuration matches the source.
Changes:
- Switched Sentry MCP definition from
command/argsto explicitcontainer/entrypoint/entrypointArgsin the source workflow. - Regenerated
.github/workflows/smoke-otel-backends.lock.ymlto reflect the new Sentry MCP container configuration.
Show a summary per file
| File | Description |
|---|---|
| .github/workflows/smoke-otel-backends.md | Makes Sentry MCP launch explicit via a Node container + npx entrypoint for reliable access to Sentry query tools. |
| .github/workflows/smoke-otel-backends.lock.yml | Recompiled workflow output to align runtime MCP gateway config (and pinned images) with the updated source workflow. |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 2/2 changed files
- Comments generated: 0
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.
Bug Fix
The smoke OTEL workflow was relying on
npxauto-containerization for the Sentry MCP server, which made Sentry span/event query tools unavailable through MCP in this path. This change makes the Sentry MCP launch explicit and updates the compiled lockfile to match.What was the bug?
smoke-otel-backendscommand: "npx"/args: [...].How did you fix it?
Explicit Sentry MCP container config
npxcommand form with an explicit containerized stdio MCP config:container: "node:lts-alpine"entrypoint: "npx"entrypointArgs: ["@sentry/mcp-server@0.33.0"]Recompiled generated workflow
.github/workflows/smoke-otel-backends.lock.ymlso the compiled workflow uses the explicit Sentry MCP container configuration.Example
Recompiled output