Compile error when installing cargo component about cargo-component

[FrankReh]

I believe the find yesterday was that the install command should use --locked and a PR was submitted and accepted yesterday too.

You may want to try cargo install cargo-component --locked if memory serves.

[calvinrp]

Merged #288 and resolved this issue.

[kajacx]

Yep, in warg-client 0.4.1 it's:

pub fn get_warg_registry(&self) -> &Option<RegistryDomain>

But in warg-client 0.4.2 (and 0.4.3) it's:

pub async fn get_warg_registry(
    &self,
    namespace: &str
) -> Result<Option<RegistryDomain>, ClientError>

I'll create an issue on the warg-client repo as well, but I think it can be "hotfixed" (for cargo component) by locking the dependency version to 0.4.1.

[kajacx]

warg-protocol also has a breaking change between 0.4.1 and 0.4.2:

// 0.4.1
pub fn namespace_state(
    &self,
    namespace: &str
) -> Result<Option<&NamespaceState>, &str>

// 0.4.2
pub fn namespace_state(&self, namespace: &str) -> Option<&NamespaceState>

[calvinrp]

We are trying to find someone with permission to yank the warg releases. The releases should have increased the minor version since there changes to the exported functions.

Also, #288 would fix.

[calvinrp]

Released 0.4.4 as a re-release of 0.4.1 that reverts the breaking changes. Also, we are in the progress of yanking 0.4.2 and 0.4.3 on crates.

[kajacx]

Also, #288 would fix.

yea, I think it would be better to just switch to the 0.5.0 version of the warg crates and be done with it.