chore(devcontainer): update image: v1.5.0-alpha.0

[tarrencev]

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

• Chores
  • Updated the Docker container image version used in development environments and GitHub Actions workflows to v1.5.0-alpha.0 for improved consistency across build, test, benchmark, and release jobs. No changes to workflow logic or configuration were made.

[coderabbitai]

Walkthrough

Ohayo sensei! This update changes the Docker image versions used in the development container configuration and several GitHub Actions workflows. The .devcontainer/devcontainer.json file and all referenced workflow jobs now use the ghcr.io/dojoengine/dojo-dev:v1.5.0-alpha.0 image instead of previous versions. No other configuration, environment variables, or workflow logic have been altered.

Changes

Files/Paths	Summary of Changes
.devcontainer/devcontainer.json	Updated Docker image version from v1.4.2 to v1.5.0-alpha.0.
.github/workflows/bench.yml .github/workflows/release-dispatch.yml	Updated container image version from v1.4.2 to v1.5.0-alpha.0 in workflow jobs.
.github/workflows/test.yml	Updated container image tag from ubuntu24/v1.4.2 to v1.5.0-alpha.0 in build, test, clippy, fmt, and docs jobs.

Possibly related PRs

• Update devcontainer image: v1.0.0-alpha.17 #2559: Updates Docker image versions in the devcontainer and CI workflows, similar in scope and files changed.
• chore(devcontainer): update image: v1.4.1 #3166: Changes Docker container image versions in devcontainer and workflows, directly related to this update.
• chore(devcontainer): update image: v1.0.6 #2802: Bumps Docker image versions in the same configuration files, reflecting similar changes.

Suggested reviewers

• glihm

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 895fc9a and c2ad267.

📒 Files selected for processing (4)

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

🔇 Additional comments (4)

.devcontainer/devcontainer.json (1)

5-5: Devcontainer image version bump
Ohayo sensei! The devcontainer image has been updated to ghcr.io/dojoengine/dojo-dev:v1.5.0-alpha.0, keeping it in sync with other workflows.

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

17-17: release-dispatch container image update
The propose-release job now uses ghcr.io/dojoengine/dojo-dev:v1.5.0-alpha.0, ensuring environment consistency for releases.

.github/workflows/bench.yml (1)

17-17: Benchmark workflow image bump
Ohayo sensei! The bench-sozo job’s container image has been updated to v1.5.0-alpha.0 to match the rest of the CI pipeline.

.github/workflows/test.yml (1)

18-18: Test workflow container updates
All jobs (build, test, clippy, fmt, docs) now reference ghcr.io/dojoengine/dojo-dev:v1.5.0-alpha.0. This aligns the test environment with the updated devcontainer and other workflows.

Also applies to: 43-43, 146-146, 160-160, 170-170

---

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 generate sequence diagram to generate a sequence diagram of the changes in 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.

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.