Skip to content

ci: Run package checks from the test.yml matrix - #1778

Merged
BYK merged 1 commit into
mainfrom
ci/package-checks-in-sentryci
Nov 1, 2026
Merged

BYK merged 1 commit into
mainfrom
ci/package-checks-in-sentryci

Conversation

@sentry-junior

@sentry-junior sentry-junior Bot commented Nov 1, 2026

Copy link
Copy Markdown
Contributor

Checks for a single package should run from the test.yml per-project matrix, set up through package.json#sentryCi. Nothing pointed contributors or agents there, so #1773 first added a standalone logger-package.yml, copying the existing mcp-server-package.yml.

  • Moves the @sentry/mcp-server clean-consumer typecheck into the matrix. It's now sentryCi.e2e: "test:package", laid out like @sentry/logger's check: test/package/check.sh plus a consumer/ fixture with the same index.ts the workflow used to write inline. mcp-server-package.yml is removed. The matrix already selects the package when it or one of its workspace dependencies (mcp-core, mcp-server-mocks, the tsconfig package) changes, and for root changes and pushes to main. The check now also sits behind the required test job; before, "Clean Consumer Typecheck" was not a required check. One small difference: matrix E2E steps run on Node 24, while the old workflow ran on Node 22.
  • Documents sentryCi. docs/operations/github-actions.md gets a "Package CI checks" section: the default script for each field, the override fields, an example, and when a separate workflow is still justified. AGENTS.md and docs/contributing/quality-checks.md add a short rule that links to it.
  • Adds a guard. scripts/workflow-policy.test.mjs, run by test:ci-projects in the quality job, fails when a workflow triggers on pull_request, pull_request_target, or merge_group and isn't on its list with a reason. The failure message points to sentryCi. The existing PR workflows are on the list: eval, install scripts, Local multi-OS E2E, PR risk, smoke tests, and token cost.

Fixes #1777

via @BYK.

--

View Session in Sentry

Move the @sentry/mcp-server clean-consumer typecheck from its own
path-filtered workflow into `sentryCi.e2e: "test:package"`, matching
@sentry/logger. The test.yml matrix already selects the package when it
or a workspace dependency changes, and its `test` job is the required
check.

Document `package.json#sentryCi` in AGENTS.md, the quality checks guide,
and the GitHub Actions guide. Add a workflow policy test that fails when
a workflow runs on pull requests without a listed reason, pointing
contributors to `sentryCi` instead.

Fixes #1777

Co-Authored-By: BYK <126780+BYK@users.noreply.github.com>
@vercel

vercel Bot commented Nov 1, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
sentry-local Ready Ready Preview Nov 1, 2026 4:20pm UTC

Request Review

@BYK
BYK enabled auto-merge (squash) November 1, 2026 16:23
@BYK
BYK merged commit 34c1ceb into main Nov 1, 2026
39 checks passed
@BYK
BYK deleted the ci/package-checks-in-sentryci branch November 1, 2026 16:32
sentry-junior Bot added a commit that referenced this pull request Nov 1, 2026
Conflicts:
- packages/mcp-core/src/server.ts: keep #1780's maxToolInputElements on
  the single SDK v2 McpServer this branch builds.
- packages/mcp-core/src/server.test.ts: keep both imports, and run
  #1780's input-cap test once, since buildServer no longer takes
  sdkVersion.
- packages/mcp-server/package.json: keep the bundle package. #1778's
  test:package consumer check typechecks the old library exports, which
  the bundle no longer ships, so drop it and its test/package files.
- package.json, AGENTS.md: keep both sides.

This branch was successfully deployed

1 active deployment
Preview — 5b5dcc94 Deployed Nov 1, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

risk: medium PR risk score: medium

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Keep package CI checks out of standalone workflows

1 participant