Packages versions
midenup 1.0.0, toolchain 0.16.0
Bug description
A component installed with midenup install <channel> --component <name> is missing from
miden help toolchain, and running it warns that it is not part of the active toolchain, even
though it is installed. Components installed this way belong to no profile, which is exactly why
they have to be named explicitly.
How can this be reproduced?
midenup install devnet --component local-registry
miden help toolchain # lists neither `local-registry` nor its `registry` alias
miden registry list # runs, but warns
Relevant log output
warning: 'registry' is an alias from component local-registry, which is installed but is not part of the current active toolchain.
Packages versions
midenup 1.0.0, toolchain 0.16.0
Bug description
A component installed with
midenup install <channel> --component <name>is missing frommiden help toolchain, and running it warns that it is not part of the active toolchain, eventhough it is installed. Components installed this way belong to no profile, which is exactly why
they have to be named explicitly.
How can this be reproduced?
Relevant log output