toolkit merge: prefixed independent releases (cli@ / mcp@)

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
52/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
github-actions, typescript
Domain
build-system, release

Research direction

Start with the product-aware bump-version command, the two .craft.yml target sets, and release.yml; review the linked plan's sections 5 and 6 first. Check how pnpm --filter can scope releases to cli or mcp while preserving the CLI nightly and registry, brew, and npm targets. Done means independent prefixed releases work for both products and the CLI documentation deployment remains release-gated.

Written by the indexing model from the issue text.

Description

Sub-task of the toolkit monorepo merge (master issue linked below). Plan: https://gist.github.com/BYK/8c0ce6cec64608f41fe5654b7827228e

Prefixed, independent releases (cli@x.y.z / mcp@x.y.z).

  • Product-aware bump-version (scope to the target product via pnpm --filter).
  • Two .craft.yml target sets; single dispatch release.yml with a product input.
  • CLI keeps -dev.N nightly scheme; registry/brew/npm targets stay under CLI config.
  • CLI docs deploy through the release-gated Craft vercel target (getsentry/craft#864); Vercel is live.

See §5 + §6.

Dominant language
TypeScript
Stars
121
Forks
14
Avg merge
22h 3m
Merged PRs (30d)
94

Contributor guide

No contributing guide indexed for this repository

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/cli

All issues in getsentry/cli

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.