Skip to content

build: Consolidate workspace dependencies and pin explicit versions#507

Open
jan-auer wants to merge 2 commits into
mainfrom
build/dependency-hygiene
Open

build: Consolidate workspace dependencies and pin explicit versions#507
jan-auer wants to merge 2 commits into
mainfrom
build/dependency-hygiene

Conversation

@jan-auer

Copy link
Copy Markdown
Member
  • Replace tokio features = ["full"] with the 7 features objectstore-server actually uses (fs, macros, net, rt-multi-thread, signal, sync, time)
  • Consolidate 28+ direct member-crate dependencies into [workspace.dependencies] as a single alphabetically-sorted block
  • Pin all abbreviated version specifiers (x.yx.y.z) and align with Cargo.lock resolved versions
  • Remove unused sentry-options workspace dependency

@codecov

This comment has been minimized.

@jan-auer jan-auer marked this pull request as ready for review June 18, 2026 15:38
@jan-auer jan-auer requested a review from a team as a code owner June 18, 2026 15:38
Comment thread clients/rust/Cargo.toml
# Pinned below workspace version for MSRV compatibility
reqwest = { version = "0.13.1", default-features = false, features = ["charset", "http2", "system-proxy", "json", "stream", "multipart"] }
sentry-core = { version = ">=0.41", features = ["client"] }
sentry-core = { workspace = true, features = ["client"] }

@lcian lcian Jun 18, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was intentionally specifying an open range so that the user could bring their own version and it would unify.
This way we're forcing users to either upgrade to 0.48.x, or if they don't notice, they will have 2 different versions, which means that the application and our objectstore-client will have 2 separate SDK states, meaning that this is not gonna work as intended.
Granted, we're only using this to propagate tracing headers.

Also this can probably be default-features = false now that I see it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants