Update Rust crate sentry to 0.36.0

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
sentry (source)	dependencies	minor	0.35.0 -> 0.36.0

---

Release Notes

getsentry/sentry-rust (sentry)

v0.36.0

Compare Source

Various fixes & improvements

• feat(sentry-tower) Make SentryLayer and SentryService Sync if request isn't (#​721) by @​syphar
• sentry-tower: Update axum dependency to v0.8 (#​718) by @​Turbo87
• Allow retrieving user of scope (#​715) by @​thomaseizinger
• Elide lifetimes where possible (#​716) by @​thomaseizinger
• Replace release bot with GH app (#​714) by @​Jeffreyhung
• Delay sampling of span to finish (#​712) by @​thomaseizinger

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

Summary by Sourcery

Build:

• Update the sentry crate dependency in packages/next-swc/crates/napi/Cargo.toml to 0.36.0.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path packages/next-swc/crates/napi/Cargo.toml --workspace
error: duplicate key `semver` in table `workspace.dependencies`
   --> Cargo.toml:125:1
    |
125 | semver = "1.0.19"
    | ^
    |
error: failed to parse manifest at `/tmp/renovate/repos/github/X-oss-byte/Nextjs/packages/next-swc/crates/napi/Cargo.toml`

Caused by:
  error inheriting `dhat` from workspace root manifest's `workspace.dependencies.dhat`

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[changeset-bot]

⚠️ No Changeset found

Latest commit: a3ed03c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[sourcery-ai]

Reviewer's Guide by Sourcery

This PR updates the sentry crate from version 0.35.0 to 0.36.0. The update includes various fixes and improvements, such as making SentryLayer and SentryService Sync, updating the axum dependency, allowing retrieval of the user scope, eliding lifetimes, and replacing the release bot with a GitHub app.

Sequence diagram showing updated span sampling behavior

sequenceDiagram
    participant App
    participant Span
    participant Sampler

    App->>Span: Create span
    Note over Span: Sampling delayed
    App->>Span: Perform operations
    App->>Span: finish()
    Span->>Sampler: Sample span
    Note over Sampler: Sampling decision made at finish

Loading

Class diagram showing updated Sentry components

classDiagram
    class SentryLayer {
      +Sync
    }
    class SentryService {
      +Sync
    }
    class Scope {
      +get_user()
    }

    note for SentryLayer "Now implements Sync trait"
    note for SentryService "Now implements Sync trait"
    note for Scope "New method to retrieve user"

Loading

File-Level Changes

Change	Details	Files
Updated the sentry crate to 0.36.0.	Changed the sentry crate version from 0.35.0 to 0.36.0 in Cargo.toml.	packages/next-swc/crates/napi/Cargo.toml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

We have skipped reviewing this pull request. Here's why:

• It seems to have been created by a bot (hey, renovate[bot]!). We assume it knows what it's doing!
• We don't review packaging changes - Let us know if you'd like us to change this.