ref: Remove orchestrion references from customer-facing surfaces - #23507
Merged
Conversation
Contributor
size-limit report 📦
|
timfish
marked this pull request as ready for review
August 24, 2026 09:33
timfish
requested review from
JPeer264,
chargome,
isaacs and
nicohrubec
and removed request for
a team
August 24, 2026 09:33
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 177723c. Configure here.
nicohrubec
approved these changes
Aug 24, 2026
Reword debug log prefixes, JSDoc on publicly re-exported symbols, and the @sentry/deno README so the internal orchestrion tooling name no longer surfaces in customer terminals, IDE hover text, or npm-rendered docs. Derive the @sentry/node bundler plugin option/return types explicitly so the emitted .d.ts stops referencing @sentry/server-utils/orchestrion symbols. No identifiers, export subpaths, hook names, or diagnostics channel names change. Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01H8UfMdJmd1kxCRkT9XC9uf
Avoids direct type imports from vite/rollup/esbuild in @sentry/node by re-exporting neutral plugin type aliases from the server-utils bundler modules, which already own those type dependencies. Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01H8UfMdJmd1kxCRkT9XC9uf
JPeer264
force-pushed
the
timfish/chore/remove-orchestrion-references
branch
from
August 25, 2026 17:53
177723c to
8ba008e
Compare
JPeer264
enabled auto-merge (squash)
August 25, 2026 17:53
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
4 participants
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.
Orchestrion is internal tooling, so this rewords debug-log prefixes (
[orchestrion:express]→[instrumentation:express]), JSDoc on publicly re-exported integrations, and the@sentry/denoREADME so the name no longer shows up in customer terminals, IDE hover text, or npm-rendered docs. The@sentry/nodebundler plugin types are now derived explicitly so the emitted.d.tsstops referencing@sentry/server-utils/orchestrionsymbols. No identifiers, export subpaths, client hook names, or diagnostics channel names change.Generated by Claude Code