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
Usually github release tarballs only contain the binary, with the expected binary name if cargo install was used. i.e. cargo-acl in this case.
I am trying to add this tool to a github action which installs from github releases, and doesnt have the ability to understand the filename in the tarball. c.f. taiki-e/install-action#604
The text was updated successfully, but these errors were encountered:
Ya, I have seen that. We prefer to use a single github action for installations, and use as few as possible over all - each one becomes SOUP and needs to be risk-accessed & documented.
I just checked and it looks like the binary is already called cargo-acl. It's in a directory that includes the version and target, but the binary has just a simple name. This is consistent with other packages like ripgrep do their releases. Perhaps you can just get tar to strip the directory when you unpack? e.g.
https://github.com/cackle-rs/cackle/releases/tag/v0.8.0 tarball contains a file
cackle-v0.8.0-x86_64-unknown-linux-musl
.Usually github release tarballs only contain the binary, with the expected binary name if
cargo install
was used. i.e.cargo-acl
in this case.I am trying to add this tool to a github action which installs from github releases, and doesnt have the ability to understand the filename in the tarball. c.f. taiki-e/install-action#604
The text was updated successfully, but these errors were encountered: