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.

Sign up for GitHub

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

Jump to bottom

Unified tooling version control #219

Open

fbac opened this issue Jul 12, 2024 · 0 comments

Contributor

fbac commented Jul 12, 2024

          nit: we rely on hardcoded versions across different workflows. It's not criticial but it would be interesting to work in a separate issue to group the versions into a single file, so there's only one source of truth when it comes to updating the tooling.

Example .versions.yaml

node: 18
go: X
slither: Y
...

Originally posted by @fbac in #212 (comment)

The text was updated successfully, but these errors were encountered:

lumtis mentioned this issue

Enable full-environment for v2 contracts #258

Closed

skosito mentioned this issue

fix: slither v2 action and slither issues #286

Merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment