Keep package CI checks out of standalone workflows #1777

test.yml builds its per-project matrix with scripts/ci-projects.mjs. Package-specific checks (e2e, test, build, and so on) are meant to go in package.json#sentryCi. Nothing steers contributors or coding agents to that before they add a workflow, so a new package can still get its own workflow that duplicates the matrix.

• feat(logger): Publish the logger as @sentry/logger #1773 first added .github/workflows/logger-package.yml to run @sentry/logger's packed-tarball check. Review caught it, and the check moved to sentryCi.e2e: "test:package".
• sentryCi is documented only in docs/operations/github-actions.md and in the header comment of scripts/ci-projects.mjs. AGENTS.md and docs/contributing/ do not mention it.
• .github/workflows/mcp-server-package.yml is a standalone workflow of the same shape: a path-filtered pull_request trigger and a clean-consumer check for one package. The logger workflow followed that example.
• No lint rule or CI check flags a new workflow that only runs checks for a single workspace package.

Raised by BYK while reviewing #1773.

via @BYK.

--

View Session in Sentry