Update devcontainer image: v1.0.0-alpha.12

[tarrencev]

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

• New Features

  • Updated Docker image version to v1.0.0-alpha.12 across multiple workflows, potentially introducing enhancements and bug fixes to the development environment.

• Bug Fixes

  • The updated Docker image may include important bug fixes that enhance overall stability and performance.

[coderabbitai]

Walkthrough

Ohayo, sensei! This pull request updates the Docker image version used across various configuration files in the project. The image version has been incremented from v1.0.0-alpha.11 to v1.0.0-alpha.12, affecting the Rust development environment and several GitHub Actions workflows. The changes ensure that the development and CI/CD pipelines utilize the latest image, which may include enhancements or bug fixes.

Changes

File Path	Change Summary
.devcontainer/devcontainer.json	Updated Docker image version from v1.0.0-alpha.11 to v1.0.0-alpha.12.
.github/workflows/bench.yml	Updated Docker image version in jobs bench-katana and bench-sozo from v1.0.0-alpha.11 to v1.0.0-alpha.12.
.github/workflows/ci.yml	Updated Docker image version in multiple jobs from v1.0.0-alpha.11 to v1.0.0-alpha.12.
.github/workflows/release-dispatch.yml	Updated Docker image version from v1.0.0-alpha.11 to v1.0.0-alpha.12.

Possibly related PRs

• Update devcontainer image: v1.0.0-alpha.11 #2403: Updates the Docker image version in .devcontainer/devcontainer.json from v1.0.0-alpha.9 to v1.0.0-alpha.11, which precedes the current update.
• bench: add sozo build bench for spawn and move #2419: Introduces a new job in .github/workflows/bench.yml that uses the Docker image ghcr.io/dojoengine/dojo-dev:v1.0.0-alpha.11, related to the version being updated.
• Prepare release: v1.0.0-alpha.12 #2436: Prepares for the release of version v1.0.0-alpha.12, directly linked to the version updated in this pull request.

---

Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between b391948 and ec83422.

Files selected for processing (4)

• .devcontainer/devcontainer.json (1 hunks)
• .github/workflows/bench.yml (2 hunks)
• .github/workflows/ci.yml (8 hunks)
• .github/workflows/release-dispatch.yml (1 hunks)

Additional comments not posted (5)

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

17-17: Ohayo sensei! Updated Docker image to v1.0.0-alpha.12

Great job updating the Docker image in the workflow. Please verify that ghcr.io/dojoengine/dojo-dev:v1.0.0-alpha.12 is available and compatible with the workflow to prevent any potential issues.

.devcontainer/devcontainer.json (1)

5-5: Ohayo, sensei! The development container image has been successfully updated.

The image version has been updated to v1.0.0-alpha.12. Please ensure that the new image is available and that it's compatible with the development environment.

.github/workflows/bench.yml (2)

17-17: Docker image updated to v1.0.0-alpha.12 for bench-katana job

The Docker image has been correctly updated to ghcr.io/dojoengine/dojo-dev:v1.0.0-alpha.12 in the bench-katana job, aligning with the PR objectives.

---

39-39: Docker image updated to v1.0.0-alpha.12 for bench-sozo job

The Docker image has been correctly updated to ghcr.io/dojoengine/dojo-dev:v1.0.0-alpha.12 in the bench-sozo job, ensuring consistency across the workflow.

.github/workflows/ci.yml (1)

34-34: Ohayo, sensei! Please verify the compatibility of the updated Docker image

It's great to see the Docker image updated to v1.0.0-alpha.12 across multiple jobs. This ensures the workflows benefit from the latest features and fixes. Please verify that this new image version is compatible with all workflows and doesn't introduce any unexpected issues.

To confirm that there are no remaining references to the old image version and ensure consistency, you can run the following script:

Also applies to: 58-58, 123-123, 138-138, 152-152, 161-161, 170-170, 179-179

Verification successful

Ohayo, sensei! Let's dig a little deeper to ensure our Docker image update is spot-on. While our first check showed no lingering references to the old version, let's double-check that the new version is present and see if there are any other images we should keep an eye on.

---

Ohayo, sensei! I've got some excellent news about our Docker image update. Let me break it down for you:

Docker image update to v1.0.0-alpha.12 successfully verified

• The new version (v1.0.0-alpha.12) is present in all relevant workflow files (.github/workflows/release-dispatch.yml, ci.yml, and bench.yml).
• No traces of the old version (v1.0.0-alpha.11) were found.
• The update has been applied consistently across 11 instances in these files.

A quick heads-up:

• There's another Docker image (debian:bookworm-slim) used in the workflows, but it's unrelated to this update.
• The devcontainer image is mentioned in devcontainer.yml, but it's separate from the dojo-dev image we've just updated. You might want to keep an eye on its updates independently.

Great job on this thorough update, sensei! Your workflows are now running on the latest dojo-dev image. 🎉

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Ensure there are no references to the old image version in the workflow files.

# Test: Search for any references to the old image version. Expect: No output if all references are updated.
rg --type yaml 'image:\s*ghcr\.io/dojoengine/dojo-dev:v1\.0\.0-alpha\.11' .github/workflows/

Length of output: 94

---

Script:

#!/bin/bash
# Description: Verify the presence of the new image version and check for other Docker images

# Test 1: Search for references to the new image version
echo "Checking for new image version (v1.0.0-alpha.12):"
rg --type yaml 'image:\s*ghcr\.io/dojoengine/dojo-dev:v1\.0\.0-alpha\.12' .github/workflows/

# Test 2: List all unique Docker images used in the workflows
echo -e "\nAll unique Docker images used:"
rg --type yaml 'image:' .github/workflows/ | sort | uniq

Length of output: 1842

---

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>, 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 generate interesting stats about this repository and render them as a table.
  -- @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 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.

Early access features: enabled

We are currently testing the following features in early access:

	- **OpenAI `o1` for code reviews**: OpenAI's new o1 model is being tested for generating code suggestions in code reviews.

	Note:
	- You can enable or disable early access features from the CodeRabbit UI or by updating the CodeRabbit configuration file.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 68.21%. Comparing base (b391948) to head (ec83422).
Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2437   +/-   ##
=======================================
  Coverage   68.20%   68.21%           
=======================================
  Files         365      365           
  Lines       48002    48002           
=======================================
+ Hits        32742    32746    +4     
+ Misses      15260    15256    -4     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.