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
I need to automate the installation of verus on a linux machine, and the fact your are using a rolling release makes pinning a particular tag/commit not possible (as the older releases are deleted). Would it be possible to keep the latest release under a consistent tag, such that I can reliably pull it from a script?
Specifically, instead of wget https://github.com/verus-lang/verus/releases/download/release%2Frolling%2F0.2025.02.06.cec767d/verus-0.2025.02.06.cec767d-x86-linux.zip one could do https://github.com/verus-lang/verus/releases/download/latest/verus-latest-x86-linux.zip
The goal is to automatically install the latest version of verus.
The text was updated successfully, but these errors were encountered:
Hello!
I need to automate the installation of verus on a linux machine, and the fact your are using a rolling release makes pinning a particular tag/commit not possible (as the older releases are deleted). Would it be possible to keep the latest release under a consistent tag, such that I can reliably pull it from a script?
Specifically, instead of
wget https://github.com/verus-lang/verus/releases/download/release%2Frolling%2F0.2025.02.06.cec767d/verus-0.2025.02.06.cec767d-x86-linux.zip
one could dohttps://github.com/verus-lang/verus/releases/download/latest/verus-latest-x86-linux.zip
The goal is to automatically install the latest version of verus.
The text was updated successfully, but these errors were encountered: