chore(devcontainer): update image: v1.7.0-alpha.2

[tarrencev]

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

• Chores
  • Updated development container and CI environments to Dojo v1.7.0-alpha.2 across build, test, docs, benchmarking, and release workflows.
  • Improves consistency between local development and CI, with more reliable and up-to-date tooling for builds and tests.

[coderabbitai]

Ohayo, sensei!

Walkthrough

Bumped the container image reference to ghcr.io/dojoengine/dojo-dev:v1.7.0-alpha.2 across the devcontainer and multiple GitHub Actions workflows. No other configuration, steps, or logic were changed.

Changes

Cohort / File(s)	Summary
Devcontainer .devcontainer/devcontainer.json	Updated image from ghcr.io/dojoengine/dojo-dev:v1.7.0-alpha.1 to ...:v1.7.0-alpha.2.
GitHub Actions workflows .github/workflows/bench.yml, .github/workflows/release-dispatch.yml, .github/workflows/test.yml, .github/workflows/validate-versions-existence.yml	Updated job container image references to ...:v1.7.0-alpha.2 (bench, propose-release, multiple test jobs). In validate-versions-existence.yml, updated from ...:v1.6.0 to ...:v1.7.0-alpha.2.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• chore(devcontainer): update image: v1.7.0-alpha.1 #3290 — Previous bump to v1.7.0-alpha.1 in the same files; this PR advances to alpha.2.
• chore(devcontainer): update image: v1.6.0 #3282 — Similar image tag updates across devcontainer and the same workflow files.
• chore(devcontainer): update image: v1.6.0-alpha.1 #3264 — Matches the pattern of updating dojo-dev image tags in devcontainer and workflows.

Suggested reviewers

• glihm

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch bump-devcontainer

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

.github/workflows/test.yml (1)

35-35: ohayo sensei — Centralize image version to reduce churn

Looks good. To avoid multi-file bumps next time, consider a reusable workflow or a repository env/var that feeds the image tag to all jobs.

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 51818f8 and 8b3bc01.

📒 Files selected for processing (5)

• .devcontainer/devcontainer.json (1 hunks)
• .github/workflows/bench.yml (1 hunks)
• .github/workflows/release-dispatch.yml (1 hunks)
• .github/workflows/test.yml (5 hunks)
• .github/workflows/validate-versions-existence.yml (1 hunks)

🔇 Additional comments (8)

.github/workflows/release-dispatch.yml (1)

27-27: ohayo sensei — Image bump looks good

Tag updated consistently here. No other logic touched.

.github/workflows/validate-versions-existence.yml (1)

18-18: ohayo sensei — Image bump acknowledged

Change is scoped to the container tag; steps remain compatible.

.github/workflows/bench.yml (1)

22-22: Ignore pinning suggestion — no dojo-dev references found
ohayo sensei — ripgrep across the entire repo didn’t locate any ghcr.io/dojoengine/dojo-dev image references (including in .github/workflows/bench.yml), so this comment isn’t applicable.

Likely an incorrect or invalid review comment.

.devcontainer/devcontainer.json (1)

5-5: ohayo sensei — Devcontainer image updated

Matches CI tag; good for parity.

.github/workflows/test.yml (4)

60-60: ohayo sensei — Image bump OK

No step changes; test job should behave identically modulo base image.

---

168-168: ohayo sensei — Image bump OK (clippy)

Consistent with other jobs.

---

182-182: ohayo sensei — Image bump OK (fmt)

All good.

---

192-192: ohayo sensei — Image bump OK (docs)

Docs job aligned with the new tag.