Skip to content

@sentry/api: package compatibility and external-consumer validation #131204

Open

Description

@BYK

Remaining v1 gates for @sentry/api (static/packages/api), carried over from getsentry/sentry-api-schema#93:

  • Supported runtime / module-resolution matrix, with packed-artifact validation in clean consumers (browser bundling, Bun, NodeNext)
  • Check documented examples against the packed entry points, and catch removed or renamed exports before release
  • Release-candidate, upgrade and deprecation guidance
  • Standalone external-consumer validation
  • Guideline: use the canonical permalink / webUrl / organizationUrl fields

Activity

  1. linear-code commented on Nov 16, 2026

    @linear-code
  2. sentry-junior commented on Nov 16, 2026

    @sentry-junior
    Contributor

    Progress on these gates, through open PRs:

  3. sentry-junior commented on Nov 16, 2026

    @sentry-junior
    Contributor

    Standalone external-consumer validation: getsentry/toolkit (the CLI and MCP server) acts as the outside consumer. It had no automatic @sentry/api bumps, so getsentry/toolkit#2291 adds a daily workflow that pins its catalog to the newest npm release and opens a PR, where toolkit's normal CI exercises the release. A per-release dispatch from this repo's bump-sentry-docs.yml can follow once a token with toolkit access is in place.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions