wathiede/letterbox
1
0
Fork 0
Code Issues 1 Pull Requests 2 Actions Releases Wiki Activity

fix(deps): update rust crate opentelemetry to 0.29.0 - autoclosed #77

Closed
renovatebot wants to merge 1 commits from renovate/opentelemetry-rust-monorepo into master
pull from: renovate/opentelemetry-rust-monorepo
merge into: wathiede:master
Conversation 1 Commits 1 Files Changed 1 +1 -1
renovatebot commented 2025-03-21 19:16:08 -07:00
Collaborator
Copy Link

This PR contains the following updates:

Package Type Update Change
opentelemetry (source) dependencies minor 0.28.0 -> 0.29.0

Release Notes

open-telemetry/opentelemetry-rust (opentelemetry)

v0.29.0

Compare Source

Released 2025-Mar-21

  • Breaking Moved ExportError trait from opentelemetry::trace::ExportError to opentelemetry_sdk::export::ExportError
  • Breaking Moved TraceError enum from opentelemetry::trace::TraceError to opentelemetry_sdk::trace::TraceError
  • Breaking Moved TraceResult type alias from opentelemetry::trace::TraceResult to opentelemetry_sdk::trace::TraceResult
  • Bug Fix: InstrumentationScope implementation for PartialEq and Hash fixed to include Attributes also.
  • Breaking changes for baggage users: #​2717
    • Changed value type of Baggage from Value to StringValue
    • Updated Baggage constants to reflect latest standard (MAX_KEY_VALUE_PAIRS - 180 -> 64, MAX_BYTES_FOR_ONE_PAIR - removed) and increased insert performance see #2284.
    • Align Baggage.remove() signature with .get() to take the key as a reference
    • Baggage can't be retrieved from the Context directly anymore and needs to be accessed via context.baggage()
    • with_baggage() and current_with_baggage() override any existing Baggage in the Context
    • Baggage keys can't be empty and only allow ASCII visual chars, except "(),/:;<=>?@&#8203;[\]{} (see RFC7230, Section 3.2.6)
    • KeyValueMetadata does not publicly expose its fields. This should be transparent change to the users.
  • Changed Context to use a stack to properly handle out of order dropping of ContextGuard. This imposes a limit of 65535 nested contexts on a single thread. See #2378 and #1887.
  • Added additional name: Option<&str> parameter to the event_enabled method
    on the Logger trait. This allows implementations (SDK, processor, exporters)
    to leverage this additional information to determine if an event is enabled.

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 has been generated by Renovate Bot.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [opentelemetry](https://github.com/open-telemetry/opentelemetry-rust/tree/main/opentelemetry) ([source](https://github.com/open-telemetry/opentelemetry-rust/tree/HEAD/opentelemetry)) | dependencies | minor | `0.28.0` -> `0.29.0` | --- ### Release Notes <details> <summary>open-telemetry/opentelemetry-rust (opentelemetry)</summary> ### [`v0.29.0`](https://github.com/open-telemetry/opentelemetry-rust/blob/HEAD/opentelemetry/CHANGELOG.md#0290) [Compare Source](https://github.com/open-telemetry/opentelemetry-rust/compare/opentelemetry-0.28.0...opentelemetry-0.29.0) Released 2025-Mar-21 - *Breaking* Moved `ExportError` trait from `opentelemetry::trace::ExportError` to `opentelemetry_sdk::export::ExportError` - *Breaking* Moved `TraceError` enum from `opentelemetry::trace::TraceError` to `opentelemetry_sdk::trace::TraceError` - *Breaking* Moved `TraceResult` type alias from `opentelemetry::trace::TraceResult` to `opentelemetry_sdk::trace::TraceResult` - Bug Fix: `InstrumentationScope` implementation for `PartialEq` and `Hash` fixed to include Attributes also. - **Breaking changes for baggage users**: [#&#8203;2717](https://github.com/open-telemetry/opentelemetry-rust/issues/2717) - Changed value type of `Baggage` from `Value` to `StringValue` - Updated `Baggage` constants to reflect latest standard (`MAX_KEY_VALUE_PAIRS` - 180 -> 64, `MAX_BYTES_FOR_ONE_PAIR` - removed) and increased insert performance see #[2284](https://github.com/open-telemetry/opentelemetry-rust/pull/2284). - Align `Baggage.remove()` signature with `.get()` to take the key as a reference - `Baggage` can't be retrieved from the `Context` directly anymore and needs to be accessed via `context.baggage()` - `with_baggage()` and `current_with_baggage()` override any existing `Baggage` in the `Context` - `Baggage` keys can't be empty and only allow ASCII visual chars, except `"(),/:;<=>?@&#8203;[\]{}` (see [RFC7230, Section 3.2.6](https://datatracker.ietf.org/doc/html/rfc7230#section-3.2.6)) - `KeyValueMetadata` does not publicly expose its fields. This should be transparent change to the users. - Changed `Context` to use a stack to properly handle out of order dropping of `ContextGuard`. This imposes a limit of `65535` nested contexts on a single thread. See #[2378](https://github.com/open-telemetry/opentelemetry-rust/pull/2284) and #[1887](https://github.com/open-telemetry/opentelemetry-rust/issues/1887). - Added additional `name: Option<&str>` parameter to the `event_enabled` method on the `Logger` trait. This allows implementations (SDK, processor, exporters) to leverage this additional information to determine if an event is enabled. </details> --- ### 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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4yMTEuMCIsInVwZGF0ZWRJblZlciI6IjM5LjIxMS4wIiwidGFyZ2V0QnJhbmNoIjoibWFzdGVyIiwibGFiZWxzIjpbXX0=-->
renovatebot commented 2025-03-21 19:16:08 -07:00
Author
Collaborator
Copy Link

⚠️ 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 server/Cargo.toml --package opentelemetry@0.28.0 --precise 0.29.0
    Updating crates.io index
error: failed to select a version for the requirement `opentelemetry = "^0.28.0"`
candidate versions found which didn't match: 0.29.0
location searched: crates.io index
required by package `xtracing v0.3.0 (registry `xinu`)`
    ... which satisfies dependency `xtracing = "^0.3.0"` (locked to 0.3.0) of package `letterbox-server v0.10.5 (/data/repos/gitea/wathiede/letterbox/server)`
### ⚠️ 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 server/Cargo.toml --package opentelemetry@0.28.0 --precise 0.29.0 Updating crates.io index error: failed to select a version for the requirement `opentelemetry = "^0.28.0"` candidate versions found which didn't match: 0.29.0 location searched: crates.io index required by package `xtracing v0.3.0 (registry `xinu`)` ... which satisfies dependency `xtracing = "^0.3.0"` (locked to 0.3.0) of package `letterbox-server v0.10.5 (/data/repos/gitea/wathiede/letterbox/server)` ```
renovatebot force-pushed renovate/opentelemetry-rust-monorepo from 8e63efb69f to e990b9e009 2025-03-30 11:31:39 -07:00 Compare
renovatebot changed title from fix(deps): update rust crate opentelemetry to 0.29.0 to fix(deps): update rust crate opentelemetry to 0.29.0 - autoclosed 2025-03-30 16:17:29 -07:00
renovatebot closed this pull request 2025-03-30 16:17:29 -07:00
Some checks failed
renovate/artifacts Artifact file update failure
Continuous integration / Check (push) Successful in 40s
Details
Continuous integration / Test Suite (push) Successful in 46s
Details
Continuous integration / Rustfmt (push) Successful in 40s
Details
Continuous integration / build (push) Successful in 1m17s
Details
Continuous integration / Trunk (push) Successful in 3m49s
Details
Continuous integration / Disallow unused dependencies (push) Failing after 2m10s
Details

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
rebase
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
ggriffiniii renovatebot wathiede
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: wathiede/letterbox#77
No description provided.
Delete Branch "renovate/opentelemetry-rust-monorepo"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?