Skip to content

publish: getsentry/sentry-java@8.44.0 #8603

Closed
Closed
publish: getsentry/sentry-java@8.44.0#8603
Labels
acceptedAdd to approve the deployci-readyCI passed, safe to publish without polling

Description

@sentry-release-bot
sentry-release-bot
bot
opened on Jun 17, 2026

Requested by: @runningcode

Merge target: (default)

Quick links:

Assign the accepted label to this issue to approve the release.

Targets

  • maven
  • github
  • registry

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

📋 Changelog

Features

  • Add enableStandaloneAppStartTracing option to send app start as a standalone transaction instead of attaching it as a child span of the first activity transaction (#5342)
    • Disabled by default; opt in via options.isEnableStandaloneAppStartTracing = true or manifest meta-data io.sentry.standalone-app-start-tracing.enable
    • Emits a transaction named App Start with op app.start, carrying the existing app start measurements and phase spans (process.load, contentprovider.load, application.load, activity lifecycle spans) as direct children of the root
    • The standalone transaction shares the same traceId as the first ui.load activity transaction so they remain linked in the trace view
    • Also covers non-activity starts (broadcast receivers, services, content providers)

Improvements

  • Reduce boxing to improve performance (#5523, #5527, #5551)
  • Replace Date with a unix timestamp in SentryNanotimeDate to improve performance (#5550)
    • SentryNanotimeDate is now marked @ApiStatus.Internal. A new (long unixDateMillis, long nanos) constructor was added, where unixDateMillis is milliseconds since the epoch. The existing (Date, long) constructor is retained but deprecated.

Dependencies

Fixes

  • Fix attachments being duplicated on native events that carry scope attachments (#5548)
  • Fix performance collector scheduling many tasks in a row (#5524)

Activity

  1. 0xadam-brown
    added
    acceptedAdd to approve the deploy
    on Jun 17, 2026
  2. getsantry
    added
    ci-pendingCI signal expected but not yet received
    on Jun 17, 2026

  3. github-actions commented on Jun 17, 2026

    @github-actions
    github-actionsBot
    on Jun 17, 2026 – with GitHub Actions

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

  4. getsantry
    added
    ci-readyCI passed, safe to publish without polling
    and removed
    ci-pendingCI signal expected but not yet received
    on Jun 17, 2026

  5. getsantry commented on Jun 17, 2026

    @getsantry
    getsantryBot
    on Jun 17, 2026

    CI checks passed for getsentry/sentry-java@8.44.0. Publishing is starting now.

  6. github-actions commented on Jun 17, 2026

    @github-actions
    github-actionsBot
    on Jun 17, 2026 – with GitHub Actions

    Publishing: run#27694615978

  7. github-actions
    removed
    acceptedAdd to approve the deploy
    on Jun 17, 2026

  8. github-actions commented on Jun 17, 2026

    @github-actions
    github-actionsBot
    on Jun 17, 2026 – with GitHub Actions

    Failed to publish. (run logs)

    Bad branch? You can delete with ease and start over.

  9. romtsn
    added
    acceptedAdd to approve the deploy
    on Jun 17, 2026
  10. getsantry
    added
    ci-pendingCI signal expected but not yet received
    and removed
    ci-readyCI passed, safe to publish without polling
    on Jun 17, 2026

  11. github-actions commented on Jun 17, 2026

    @github-actions
    github-actionsBot
    on Jun 17, 2026 – with GitHub Actions

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

  12. getsantry
    added
    ci-readyCI passed, safe to publish without polling
    and removed
    ci-pendingCI signal expected but not yet received
    on Jun 17, 2026

  13. getsantry commented on Jun 17, 2026

    @getsantry
    getsantryBot
    on Jun 17, 2026

    CI checks passed for getsentry/sentry-java@8.44.0. Publishing is starting now.

  14. github-actions commented on Jun 17, 2026

    @github-actions
    github-actionsBot
    on Jun 17, 2026 – with GitHub Actions

    Publishing: run#27702516086

  15. github-actions commented on Jun 17, 2026

    @github-actions
    github-actionsBot
    on Jun 17, 2026 – with GitHub Actions

    Published successfully: run#27702516086

  16. github-actions
    closed this as completedon Jun 17, 2026
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

    acceptedAdd to approve the deployci-readyCI passed, safe to publish without polling

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions