Skip to content

publish: getsentry/sentry-electron@7.14.0 #8611

Closed

Description

@sentry-release-bot

Requested by: @timfish

Merge target: (default)

Quick links:

Assign the accepted label to this issue to approve the release.
To retract the release, the person requesting it must leave a comment containing #retract on a line by itself under this issue.

Targets

  • npm
  • registry
  • github

Checked targets will be skipped (either already published or user-requested skip). Uncheck to retry a target.


📋 Changelog

New Features ✨

  • Update SDKs and migrate to dataCollection by @timfish in #1388
  • Update Sentry SDKs to v10.56.0 by @github-actions in #1381
  • Update Sentry SDKs to v10.55.0 by @github-actions in #1375
  • Update Sentry SDKs to v10.53.1 by @github-actions in #1369
  • Update Sentry SDKs to v10.51.0 by @github-actions in #1363

Bug Fixes 🐛

  • (net) Propagate correct distributed tracing IDs by @lcian in #1389

Internal Changes 🔧

Deps

Deps Dev

Other

  • New Electron versions by @github-actions in #1383
  • New Electron versions by @github-actions in #1380
  • New Electron versions by @github-actions in #1368
  • Enable type-aware linting by @timfish in #1373
  • Modernize TypeScript configuration by @timfish in #1372
  • Lint - Re-enable typescript/no-explicit-any by @timfish in #1367
  • Lint - Re-enable typescript/consistent-type-imports by @timfish in #1366
  • New Electron versions by @github-actions in #1364

Activity

  1. github-actions commented on Jun 18, 2026

    @github-actions

    Approved. Checking CI status on the release branch. Publishing will start automatically when CI passes.

  2. added
    ci-failedCI checks failed on the release branch
    and removed
    acceptedAdd to approve the deploy
    ci-pendingCI signal expected but not yet received
    on Jun 18, 2026
  3. getsantry commented on Jun 18, 2026

    @getsantry

    CI checks failed for getsentry/sentry-electron@7.14.0 (63862ce9). Publishing is blocked.

    Failed checks: All required jobs passed or were skipped, E2E Tests (macos-latest, 28.3.3, 3), E2E Tests (macos-latest, 28.3.3, 2), E2E Tests (windows-2022, 37.10.3, 3), E2E Tests (macos-latest, 28.3.3, 4), E2E Tests (macos-latest, 28.3.3, 1), E2E Tests (windows-2022, 28.3.3, 2), E2E Tests (windows-2022, 28.3.3, 3), E2E Tests (windows-2022, 28.3.3, 1), E2E Tests (windows-2022, 30.5.1, 2), E2E Tests (windows-2022, 28.3.3, 4), E2E Tests (ubuntu-22.04, 28.3.3, 1), E2E Tests (ubuntu-22.04, 28.3.3, 3), E2E Tests (ubuntu-22.04, 28.3.3, 4), E2E Tests (ubuntu-22.04, 28.3.3, 2)

    View check runs

    Re-add the accepted label once CI is fixed to retry.

  4. timfish commented on Jun 18, 2026

    @timfish
    Collaborator

    #retract

  5. lcian commented on Jun 18, 2026

    @lcian
    Member

    #retract

  6. timfish commented on Jun 18, 2026

    @timfish
    Collaborator

    #retract no worky

  7. timfish commented on Jun 18, 2026

    @timfish
    Collaborator

    @BYK do you know why #retract isn't working?

  8. BYK commented on Jun 18, 2026

    @BYK
    Member

    @timfish we removed retract as now you can simply close the issue?

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

    ci-failedCI checks failed on the release branch

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions