Skip to content

Update Rust crate pyroscope to v1#420

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/pyroscope-1.x
Open

Update Rust crate pyroscope to v1#420
renovate[bot] wants to merge 1 commit intomainfrom
renovate/pyroscope-1.x

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Mar 1, 2026

This PR contains the following updates:

Package Type Update Change
pyroscope (source) dependencies major 0.5.81.0.0

Release Notes

pyroscope-io/pyroscope-rs (pyroscope)

v1.0.0

Breaking Changes

  • Removed auth_token from Python and Ruby FFI bindings and related code
  • Removed detect_subprocesses from Python and Ruby configs
  • Config constructor now requires app/spy identity and sample rate inputs
  • Removed support for collapsed format
  • Removed global tags from ruleset

New Features

  • Integrated pprof-rs backend into main crate behind optional backend-pprof-rs feature
  • Switched to push API (from /ingest to /push)
  • Generated push API protos
  • Added ThreadId type
  • Added rustls-no-provider TLS feature

Bug Fixes / Improvements

  • Unified signal logic
  • Report cleanup functions
  • Optimized ruleset
  • Removed obscure thread id hash check
  • Ruby: inline thread_id crate; remove detect_subprocess
  • Dependency updates (reqwest 0.13, prost 0.14, thiserror 2.0, serde_json 1.0.115, uuid 1.20, libflate 2.1)

Configuration

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

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, 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.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Mar 1, 2026
@renovate
Copy link
Contributor Author

renovate bot commented Mar 1, 2026

⚠️ Artifact update problem

Renovate failed to update artifacts 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 client/Cargo.toml --package pyroscope@0.5.8 --precise 1.0.1
    Updating crates.io index
error: failed to select a version for the requirement `pyroscope = "^0.5.7"`
candidate versions found which didn't match: 1.0.1
location searched: crates.io index
required by package `pyroscope_pprofrs v0.2.10`
    ... which satisfies dependency `pyroscope_pprofrs = "^0.2.10"` of package `client v0.1.0 (/tmp/renovate/repos/github/boardgamers/clash/client)`

File name: Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path server/Cargo.toml --package pyroscope@0.5.8 --precise 1.0.1
    Updating crates.io index
error: failed to select a version for the requirement `pyroscope = "^0.5.7"`
candidate versions found which didn't match: 1.0.1
location searched: crates.io index
required by package `pyroscope_pprofrs v0.2.10`
    ... which satisfies dependency `pyroscope_pprofrs = "^0.2.10"` of package `client v0.1.0 (/tmp/renovate/repos/github/boardgamers/clash/client)`

@renovate renovate bot enabled auto-merge (squash) March 1, 2026 11:19
@renovate renovate bot force-pushed the renovate/pyroscope-1.x branch from 12a1bc5 to 83c1d20 Compare March 1, 2026 21:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants