Due to a human error version 3.6.x has been published instead of the correct 0.3.6 version number. This is an issue as now the test setup listening to the unstable channel always installs the 3.6.x version instead of any new version with a lower version number (e.g. 0.3.7).
There is no way to delete a package or demote it to an unused channel
There is no way to create a channel via public builder
the usage of cli (0.6.21) is not actually very clear, as described below and still leads to the wrong package being installed
hab bldr channel create -o myorigin deprecated
✗✗✗ No auth token specified
hab bldr channel create -o myorigin --auth my token deprecated
error: Found argument ‘–auth’ which wasn’t expected, or isn’t valid in this context
hab bldr channel create --help
Creates a new channel
hab bldr channel create [OPTIONS]
-h, --help Prints help information
-V, --version Prints version information
-u, --url <BLDR_URL> Specify an alternate Builder endpoint. If not specified, the value will be taken from the
HAB_BLDR_URL environment variable if defined. (default: https://bldr.habitat.sh)
-o, --origin Sets the origin to which the channel will belong. Default is from ‘HAB_ORIGIN’ or cli.toml
The channel name
It seems like there is no way to specify the token with the channel command. The only way to fix this is to provide the token via an environment variable.
Now we can finally move on to promoting the offending packages to the deprecated channel one at a time via the cli. However, if now I run
hab svc unload mypkg and then
hab svc load --channel unstable mypkg, we end up with the old package from the deprecated channel. How does one correctly fix a situation like that?