ci: fix dependabot alerts

[Thegaram]

1. Purpose or design rationale of this PR

Fix dependabot alerts, reported on https://github.com/scroll-tech/sequencer.

2. PR title

Your PR title must follow conventional commits (as we are doing squash merge for each PR), so it must start with one of the following types:

• ci: Changes to our CI configuration files and scripts (example scopes: vercel, github, cypress)

3. Deployment tag versioning

Has the version in params/version.go been updated?

• This PR doesn't involve a new deployment, git tag, docker image tag, and it doesn't affect traces

4. Breaking change label

Does this PR have the breaking-change label?

• This PR is not a breaking change

Summary by CodeRabbit

• Chores
  • Upgraded several automation workflows to the latest available versions for improved build, test, and deployment reliability. These updates help ensure that the development process benefits from recent performance improvements and stability enhancements.

[coderabbitai]

Walkthrough

This pull request updates several GitHub Actions workflow files to use newer versions of various actions. The changes include bumping the version of the Node setup action, updating the checkout action across multiple workflows, and revising several Docker-related actions. In addition, the Go setup action is updated in one workflow file. The modifications solely change version references without altering the underlying workflow logic.

Changes

Files	Change Summary
.github/workflows/bump_version.yml	Upgraded actions/setup-node from v3 to v4.
.github/workflows/docker-arm64.yml, .github/workflows/docker.yaml, .github/workflows/l2geth_ci.yml, .github/workflows/semgrep.yml	Upgraded actions/checkout: from v2 to v4 in docker and l2geth_ci files, and from v3 to v4 in semgrep.
.github/workflows/docker-arm64.yml, .github/workflows/docker.yaml	Updated Docker actions: upgraded docker/setup-buildx-action from commit for v2.10.0 to commit for v3.10.0, and docker/login-action from commit for v3.3.0 to commit for v3.4.0; additionally, in docker.yaml, updated docker/setup-qemu-action from commit for v2.2.0 to commit for v3.6.0.
.github/workflows/l2geth_ci.yml	Upgraded actions/setup-go from v2 to v5.

Sequence Diagram(s)

Possibly related PRs

• ci: add zizmor #1146: Updates the version of the Node setup action in the workflow, similar to the changes made in .github/workflows/bump_version.yml.

Suggested labels

bump-version

Suggested reviewers

• colinlyguo
• georgehao

Poem

I'm a bunny with a coding flair,
Hopping through workflows with updates to spare.
New versions bloom like springtime carrots bright,
My hops celebrate each action's new light.
Cheers from the burrow—code on, day and night!

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 019e52c and 68a0313.

📒 Files selected for processing (5)

• .github/workflows/bump_version.yml (1 hunks)
• .github/workflows/docker-arm64.yaml (2 hunks)
• .github/workflows/docker.yaml (2 hunks)
• .github/workflows/l2geth_ci.yml (7 hunks)
• .github/workflows/semgrep.yml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: test
• GitHub Check: Analyze (go)

🔇 Additional comments (11)

.github/workflows/semgrep.yml (1)

24-24: Checkout Action Version Upgrade
The checkout action version has been updated from v3 to v4. This upgrade is consistent with similar changes across other workflow files and should provide the latest features and fixes.

.github/workflows/bump_version.yml (1)

57-59: Setup-Node Action Version Upgrade
The setup-node action has been updated to v4 (line 59). This change aligns the node setup across workflows and reflects the recent upgrades applied project-wide.

.github/workflows/docker-arm64.yaml (3)

22-23: Checkout Action Version Upgrade
The checkout step now uses actions/checkout@v4, ensuring consistency with other workflow files.

---

32-34: Docker Buildx Action Version Update
The docker/setup-buildx-action version is updated to v3.10.0. This pinning to a specific commit ensures stability and should bring in the latest improvements.

---

38-39: Docker Login Action Version Update
The docker/login-action has been updated to v3.4.0. This change likely includes security and feature enhancements.

.github/workflows/l2geth_ci.yml (2)

23-26: Upgrade Go Setup Action to v5
Multiple instances of the Go installation steps have been updated to use actions/setup-go@v5. This update standardizes the environment setup across jobs. Note that in the goimports-lint job, the go-version is set to 1.18.x—which appears intentional for compatibility reasons.

Also applies to: 42-44, 70-73, 90-93, 117-120, 141-144

---

28-30: Upgrade Checkout Action to v4
All checkout steps across various jobs have been updated to actions/checkout@v4. This ensures a consistent and modern checkout process throughout the CI workflows.

Also applies to: 54-56, 75-77, 98-100, 122-124, 146-148

.github/workflows/docker.yaml (4)

16-18: Checkout Action Version Upgrade
The checkout action is updated to actions/checkout@v4, aligning with the versions used in other workflow files for consistency.

---

21-23: QEMU Setup Action Upgrade
The docker/setup-qemu-action has been updated to version v3.6.0. This upgrade should enhance multi-architecture support for the builds.

---

24-26: Docker Buildx Action Version Update
The docker/setup-buildx-action has been upgraded to v3.10.0. This improves build capabilities and is in line with updates across other workflow files.

---

40-42: Docker Login Action Version Update
The docker/login-action has been updated to v3.4.0, which should provide improved authentication handling and security features.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• 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 testing code 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

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 using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• 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/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.