-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compile error when installing cargo component #293
Comments
Yep, in pub fn get_warg_registry(&self) -> &Option<RegistryDomain> But in pub async fn get_warg_registry(
&self,
namespace: &str
) -> Result<Option<RegistryDomain>, ClientError> I'll create an issue on the |
I believe the find yesterday was that the install command should use You may want to try |
We are trying to find someone with permission to yank the Also, #288 would fix. |
Released |
yea, I think it would be better to just switch to the |
Merged #288 and resolved this issue. |
Recently, I got an error when I was installing
cargo component
in GitHub actions. The error is:This happens for version
0.10.1
(see here) as well as0.11.0
(see here). I get the same error when I install on my Windows 10 computer with--force
.I think the install command was working fine a week or two ago, so my first guess would be that a dependency crate released a new minor version with breaking changes (not following semver), and cargo install is now fetching that new version and the build fails because of the breaking change.
EDIT:
You can install
cargo component
with the lock file usingThe text was updated successfully, but these errors were encountered: