Release sentry and @sentry/mcp-server after the @sentry/api switch

Open
#1,877 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
github-actions, node.js, typescript
Domain
cli, devtools, release

Research direction

Read the linked task 8.10 in openspec/changes/unify-sentry-api-layer/tasks.md, then review the release setup and the versioning.files change in #1825. Run one Craft release that publishes sentry and @sentry/mcp-server together, install both packages from npm, and check that sentry mcp and npx @sentry/mcp-server respond to initialize and tools/list; file or fix any Craft or versioning issues found.

Written by the indexing model from the issue text.

Description

CLI MCP

Part of #1357. Plan: unify-sentry-api-layer task 8.10 (tasks). Depends on #1876.

Why

There has been no toolkit release since [email protected], and npm still has @sentry/[email protected]. Releasing right after the client moves into @sentry/api ships that change on its own, before the CLI wrapper migration and the MCP command surface start changing behavior. It is also the first real run of Craft 3.8's versioning.files (#1825).

Done when

  • sentry and @sentry/mcp-server are published from one Craft run.
  • Both install from npm, and sentry mcp and npx @sentry/mcp-server answer initialize and tools/list.
  • Any Craft or versioning problems found are fixed or filed.

via @BYK.

--

View Session in Sentry

Dominant language
TypeScript
Stars
961
Forks
179
Avg merge
15h 33m
Merged PRs (30d)
476

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getsentry/toolkit

All issues in getsentry/toolkit

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.