Skip to content

Dependency updates - #3749

Closed
itowlson wants to merge 2 commits into
spinframework:mainfrom
itowlson:patch-all-the-things-again-again
Closed

itowlson wants to merge 2 commits into
spinframework:mainfrom
itowlson:patch-all-the-things-again-again

Conversation

@itowlson

Copy link
Copy Markdown
Contributor

See the Cargo.lock diffs.

I wasn't able to get rid of all the old versions of the TLS etc. libraries, because they are deep down an transitive dep chain from things that have not yet updated. Happy to take advice or recommendations from anyone who knows about this sort of thing.

Signed-off-by: itowlson <ivan.towlson@fermyon.com>
@itowlson

Copy link
Copy Markdown
Contributor Author

There's a maddening dependency chain around the AWS libraries which via hyper-rustls 0.24 end up depending on rustls 0.21 and refuse to be shifted, and I am not sure if there is anything we can do about this.

Signed-off-by: itowlson <ivan.towlson@fermyon.com>
@itowlson

Copy link
Copy Markdown
Contributor Author

I bumped a few more but there is some stuff where the most recent version of a dependency still has a crime crate as one of its own dependencies, and the crime crate either has no fixed version, or the parent is not compatible with the fixed version.

@itowlson
itowlson enabled auto-merge October 22, 2026 04:27
@itowlson

Copy link
Copy Markdown
Contributor Author

ugh this falls afoul of rustls not being able to decide which crypto provider to use

@itowlson itowlson closed this Oct 22, 2026
auto-merge was automatically disabled October 22, 2026 18:23

Pull request was closed

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.

1 participant