chore: bump docker-compose-types from 0.22 to 0.23#936
Closed
georgesfarah wants to merge 1 commit into
Closed
Conversation
docker-compose-types 0.23.0 makes serde_yaml optional (behind the `yaml` feature) and relaxes its version constraint from `=0.9.33` to `^0.9.33`, fixing a conflict when the workspace uses serde_yaml >=0.9.34.
✅ Deploy Preview for testcontainers-rust ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
DDtKey
approved these changes
Apr 14, 2026
DDtKey
approved these changes
Apr 14, 2026
DDtKey
left a comment
DDtKey
left a comment
Contributor
There was a problem hiding this comment.
Thank you for the contribution!
Contributor
|
Sorry, closing in favor of #931 as it's duplicate |
Author
|
Its okay! @DDtKey When are you planning to cut a new release? |
Contributor
|
I'm about to do it today or tomorrow. |
Author
|
Thank you! |
Contributor
|
@georgesfarah it's been released! |
Author
|
Thank you! |
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.
Summary
Bumps
docker-compose-typesfrom0.22to0.23.Motivation
docker-compose-types 0.22.0hardcodes itsserde_yamldependency to the exact version=0.9.33. This strict pin means any workspace that transitively depends on bothtestcontainers(with thedocker-composefeature) and a crate requiringserde_yaml >= 0.9.34will fail to resolve dependencies entirely — Cargo cannot satisfy both constraints simultaneously.docker-compose-types 0.23.0fixes this in two ways:serde_yamlis now optional, gated behind theyamlfeature (which remains on by default for backwards compatibility)=0.9.33to^0.9.33, allowing any compatible0.9.xreleaseThe fix was made in stephanbuys/docker-compose-types#64 and released as
0.23.0.Because
testcontainersdeclaresdocker-compose-types = "0.22", Cargo's semver resolution restricts it to>=0.22.0, <0.23.0and will never pick up the fixed0.23.0release without this bump. Updatingtestcontainersto"0.23"is therefore required to let downstream workspaces benefit from the fix.Test plan