Pin maybe-async-cfg to version 0.2.4 due to breaking changes in latest. #218
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.
With the configuration currently in master
Will use the latest
maybe-async-cfg
which is0.2.5
. This causes compilation errors.This change pins the version to
=0.2.4
rather than attempting to upgrade to the latest version. I'll leave that as an excersise to someone with more experience with maybe-async-cfg.--
Details about the errors encountered:
When 0.2.5 is selected we see the following compilation errors and many other similar ones: