Bump socketioxide from 0.18.2 to 0.18.3 in /scylla-server#639
Merged
bracyw merged 2 commits intoMay 20, 2026
Conversation
dependabot
Bot
added
dependencies
Bumps [socketioxide](https://github.com/totodore/socketioxide) from 0.18.2 to 0.18.3. - [Release notes](https://github.com/totodore/socketioxide/releases) - [Changelog](https://github.com/Totodore/socketioxide/blob/main/CHANGELOG.md) - [Commits](Totodore/socketioxide@socketioxide-v0.18.2...socketioxide-v0.18.3) --- updated-dependencies: - dependency-name: socketioxide dependency-version: 0.18.3 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/cargo/scylla-server/socketioxide-0.18.3
branch
from
9637e3a to
987e232
Compare
socketioxide 0.18.3 declares socketioxide-core ^0.18 and socketioxide-parser-common ^0.17. The resolver locked parser-common to 0.17.0, which depends on socketioxide-core 0.17 — producing two incompatible versions of the core Parse trait and 8 E0599 errors on CommonParser methods (encode_value, decode_value, decode_default, read_event, …). Upstream republished parser-common as 0.17.1 against core 0.18. Pinning the lock to that resolves the duplicate core version. https://claude.ai/code/session_0159LgZ35SzCrsoWgwv85nqY
dependabot
Bot
deleted the
dependabot/cargo/scylla-server/socketioxide-0.18.3
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps socketioxide from 0.18.2 to 0.18.3, and pins the transitive
socketioxide-parser-commonto 0.17.1 so the build resolves to a singlesocketioxide-core 0.18.0.Why the extra commit
socketioxide 0.18.3declaressocketioxide-core = "^0.18"andsocketioxide-parser-common = "^0.17". Dependabot's resolver leftparser-commonat the previously-locked0.17.0, which depends onsocketioxide-core 0.17.0— producing two incompatible versions of the coreParsetrait in the graph and 8×E0599errors onCommonParsermethods (encode_value,decode_value,decode_default,read_event, …).Upstream republished
socketioxide-parser-common 0.17.1againstcore 0.18on 2026-04-12. Bumping it inCargo.lockcollapses the graph back to a singlesocketioxide-core 0.18.0and the build passes.Changes
scylla-server/Cargo.toml:socketioxide0.18.2 → 0.18.3scylla-server/Cargo.lock:socketioxide-parser-common0.17.0 → 0.17.1;socketioxide-core 0.17.0removed; incidentaltempfile/getrandomreshuffle from the resolverVerification
cargo tree -i socketioxide-core→ single entry,0.18.0cargo clippy --all-targetscleancargo fmt --checkcleansocketioxide 0.18.3 release notes
Full changelog