[sentry-junior]

Rollout: sentry → sentry-server, getsentry → getsentry-server

Why: the new Sentry CLI ships a binary named sentry, which the server's console script shadows. Same rollout across all PRs below; keep this section in sync.

Phase 1: add new names and keep the old names as deprecated aliases (merge first)

• getsentry/sentry: feat(runner): Add sentry-server and deprecate the sentry console script #129100 (this PR). Adds sentry-server, keeps the sentry alias, moves in-repo callers

Phase 2: move callers to the new names (after phase 1)

• getsentry/getsentry#22824: adds getsentry-server (keeps getsentry alias) and moves callers. Needs Requires on the sentry PR for CI; image builds need sentry-version bumped past the phase 1 merge
• ref: Call Sentry server binary as sentry-server self-hosted#4600: after sentry-server ships in the nightly image
• getsentry/sentry-docsfeat(workflow): Support -1 for all org projects properly #20297: after phase 1; self-hosted pages after the self-hosted release that includes it
• getsentry/ops: PR TBD (audit in progress). Prod k8s/cron/job manifests calling sentry/getsentry

Phase 3: remove the aliases (only after prod manifests and self-hosted are confirmed off the old names)

• getsentry/sentry: drop the sentry alias and clean up stale .venv/bin/sentry (TBD)
• getsentry/getsentry: drop the getsentry alias (TBD)
• Heads-up to sentry-kubernetes/charts (18+ templates use command: ["sentry"]) before the sentry alias is removed

Adds a sentry-server console script and keeps sentry as a deprecated alias, both pointing at sentry.__main__:main.

The new Sentry CLI (getsentry/cli) also installs a sentry binary, and the server's console script shadows it. This PR moves every in-repo caller to sentry-server: devservices programs, devserver daemons, devenv/sync.py, scripts/lib.sh, the Makefile, CI workflows, the self-hosted Dockerfile and entrypoint, .vscode/launch.json, the click prog name (Usage: sentry-server …), user-facing messages, and agent/dev docs.

It also removes the .envrc and package.json postinstall logic that deleted node_modules/.bin/sentry and died on any other sentry binary on PATH, so the npm CLI is no longer actively deleted. .envrc now checks for .venv/bin/sentry-server.

Compatibility

• sentry stays in setup.cfg, so dev venvs and images ship both names. getsentry builds against sentry master and its image, CI, GoCD jobs, and bin/options/* still call sentry directly. So do ops manifests and self-hosted.
• docker_entrypoint.py prepends sentry-server for bare subcommands and wraps both sentry and sentry-server in tini.
• #!/usr/bin/env sentry exec scripts keep working through the alias, but should move to sentry-server exec.

Merge order: this PR lands first. getsentry/getsentry#22824 follows. Alias removal is a later phase 3 PR, after getsentry, ops manifests, and self-hosted are confirmed off sentry. Dev shadowing is only fully fixed in phase 3: the venv's sentry alias still ranks ahead of the CLI on PATH until then. Phase 3 also has to delete the stale .venv/bin/sentry script, because tools/fast_editable.py never removes old console scripts.

Changelog Entry

• Add sentry-server as the Sentry server command. sentry still works as a deprecated alias and will be removed in a future release; update scripts, including #!/usr/bin/env sentry exec hashbangs, to use sentry-server.

via @joshuarli.

--

View Junior Session [Sentry]

[github-actions]

🚨 Warning: This pull request contains Frontend and Backend changes!

It's discouraged to make changes to Sentry's Frontend and Backend in a single pull request. The Frontend and Backend are not atomically deployed. If the changes are interdependent of each other, they must be separated into two pull requests and be made forward or backwards compatible, such that the Backend or Frontend can be safely deployed independently.

Have questions? Please ask in the #discuss-dev-infra channel.