You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using cargo-dist to package multiple binaries from a repository, oranda picks up each shell script installer and places them all on the main page this happens regardless if you are using oranda-workspace.json or not. Each page continues to have installers for all applications in the repository.
Looking through previous discussion on this topic, I found a similar issue #650. #650 resolved this problem by releasing each package separately, giving them tags like package-name/vX.X.X. I would like to release my whole repository at once under one tag, so this work around not appealing to my use case. I am using the Unified release workflow as described in cargo-dist's documentation
The text was updated successfully, but these errors were encountered:
When using cargo-dist to package multiple binaries from a repository, oranda picks up each shell script installer and places them all on the main page this happens regardless if you are using oranda-workspace.json or not. Each page continues to have installers for all applications in the repository.
Screenshot
This problem can be seen live at https://kestrel.aeroteameindhoven.nl/, the repository is https://github.com/aeroteameindhoven/kestrel
Looking through previous discussion on this topic, I found a similar issue #650. #650 resolved this problem by releasing each package separately, giving them tags like
package-name/vX.X.X
. I would like to release my whole repository at once under one tag, so this work around not appealing to my use case. I am using the Unified release workflow as described in cargo-dist's documentationThe text was updated successfully, but these errors were encountered: