Calvin Prewitt

Yes, it makes sense to have wrappers live in `wasm-tools` and publish the `wasm-tools` components from that repo. This is on our radar and we want this as well. We...

Closing this PR. The `wit` CLI functionality is in the process of moving over to https://github.com/bytecodealliance/wasm-pkg-tools

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, https://github.com/bytecodealliance/cargo-component/pull/288...

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.

Merged #288 and resolved this issue.

There's a few ways to do it. All this needs to be better documented. Worth noting, that the `wasi:http` bindings generated are very low-level and not ergonomic. Work is under...

Currently, there isn't a user config option to set a namespace mapping to a registry domain. This namespace mapping is only for hint header accepted mappings and operator log import...

Thanks for pointing this out as confusing. Do you think it should be renamed? Or just requires clearer description and messaging in the CLI?

In #290 PR, added a confirmation message that defaults to `no` ``` `Yank` revokes a version, making it unavailable. It is permanent and cannot be reversed. Yank `{version}` of `{package}`?...

Reproducible / verifiable build from source is a desirable property for package distribution. I was thinking it can be implemented by CI/CD type of services that publish on top of...