New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reduce size of manifests #36
Comments
Some ideas for reducing size:
|
Thanks for your ideas.
We already use the template in the base manifest, so leaving it in the manifest might work well.
Interesting. I'm not sure what the latter means exactly, but currently releases other than the
Given that we support packages other than Rust, and our manifest generator also does things like getting file hashes, etc., I don't see much advantage from a view of maintenance cost in doing this for tools we officially support. |
You are welcome.
I notice that other softwares, such as cargo-nextest, also shares the same pattern, so I think this alone would significantly reduce the size.
For the "compress" part, I mean that we could compress these json files and the scripts with something like zstd, which has very fast decompression speed and I remember its decompression speed is not related to the options passed to compression, that means we might be able to use highest level. Then we can include a script that extracts this and runs the main.sh
That's true. |
Implemented the following three patches:
I think this is fine for now. |
Since #27, we manage tool info as JSON manifests.
However, the manifest size is currently not very optimized.
From some quick tests, it does not appear that the manifest size is affecting the download time of the action itself at this time, but this could become an issue as more tools are supported.
@latest
). It appears to make sense to replace this with a reference to the corresponding version.The text was updated successfully, but these errors were encountered: