fix: cacache build without async runtime by enabling tokio-runtime
#1341
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.
Description
Enable the
tokio-runtimefeature for thecacachedependency ingit-cliff-core.Motivation and Context
In the workspace root,
cacacheis already resolved with an async runtime enabled due to transitive dependencies from the CLI:However, when building
git-cliff-corein isolation,cacacheis currently resolved without any async runtime enabled:As a result, cargo build succeeds at the workspace level, but
cargo msrv -p git-cliff-core checkfails due to missing runtime-dependent types incacache.Additional context
Stateis undefined when neithertokionorasync-stdfeatures are enabled zkat/cacache-rs#92How Has This Been Tested?
cargo buildforgit-cliff-corecargo buildfor the workspacecargo msrvto verify the configuration builds correctly under MSRV constraintsScreenshots / Logs (if applicable)
N/A
Types of Changes
Checklist: