-
Notifications
You must be signed in to change notification settings - Fork 53
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
Version pin foundry #116
Labels
Comments
kayabaNerve
added a commit
that referenced
this issue
Sep 17, 2022
The above pinned fmt/clippy yet didn't create a script for a monthly PR, nor did it pin the wasm toolchain (which is on nightly). I'm also unsure if we can pin foundry, which wasn't handled here. |
kayabaNerve
added a commit
that referenced
this issue
Sep 18, 2022
Rust is now fully pinned. It appears foundry cannot be pinned at this time, unless we build it from source (dropping the provided action) AND that'll have to be via the git commit as an ID. |
Closed
davidjohnbell
pushed a commit
to econsta/serai
that referenced
this issue
Nov 20, 2023
Fixes serai-dex#116 and serai-dex#441.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
foundry recently updated, and in doing so, broke our CI requiring the following fix: 8d56c43
The fix was beneficial, making this arguably for the better, yet unappreciated as it caused unrelated comments to error for no reason.
#114 similarly errored due to a new version of nightly. While the fixes it mandated were appreciated, it's abruptness wasn't.
Perhaps its pinned with a job to update them every month? Then we'd have an automatic PR prompting us and we can respond to newly caught issues with it.
The text was updated successfully, but these errors were encountered: