ci: use ci-builder image for slither

[mds1]

Updates the slither github action to use CI builder, so our pinned version of foundry is used, instead of the latest version.

@ethereum-optimism/contract-reviewers Please note that now when updating the CI builder image in .circleci/config.yml we'll also need to update it here

[coderabbitai]

Walkthrough

Walkthrough

The update involves transitioning the CI workflow's execution environment from the default ubuntu-latest runner to a specific Docker image, us-docker.pkg.dev/oplabs-tools-artifacts/images/ci-builder:v0.43.0. This change aims to enhance standardization and potentially provide better control and consistency during CI runs.

Changes

File Path	Change Summary
.github/workflows/slither.yml	Switched execution environment to us-docker.pkg.dev/oplabs-tools-artifacts/images/ci-builder:v0.43.0

Related issues

• ci: add docker CLI to ci-builder image #8529: This PR demonstrates a proactive approach by incorporating essential tools (like Docker CLI) directly into the ci-builder image, aligning with the suggestion to enrich the CI environment by integrating more tools into the ci-builder image itself.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

---

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit-tests for this file.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit tests for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[mds1]

Hm maybe this didn't work? Seems the slither-analyze job is stuck, cc @raffaele-oplabs

Switching PR to draft in the meantime

[mds1]

Ok this is working as expected, now thanks @raffaele-oplabs!