Update devcontainer image: v1.0.0-alpha.15

[tarrencev]

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

• New Features

  • Updated Docker image version to v1.0.0-alpha.15, enhancing overall performance and stability.

• Bug Fixes

  • Minor adjustments made to YAML indentation for improved readability in CI workflows.

[coderabbitai]

Walkthrough

Ohayo, sensei! The changes in this pull request involve updating the Docker image version from v1.0.0-alpha.14 to v1.0.0-alpha.15 across several configuration files. The updates are reflected in the .devcontainer/devcontainer.json, .github/workflows/bench.yml, .github/workflows/ci.yml, and .github/workflows/release-dispatch.yml files, where the specific jobs using the Docker image have been modified to reference the new version. No new jobs were added, nor were any existing jobs removed.

Changes

File Path	Change Summary
.devcontainer/devcontainer.json	Updated image version to v1.0.0-alpha.15.
.github/workflows/bench.yml	Updated image version for bench-katana and bench-sozo jobs.
.github/workflows/ci.yml	Updated image version for multiple jobs: test, ensure-wasm, dojo-core-test, dojo-spawn-and-move-example-test, dojo-world-bindings-check, clippy, fmt, and docs. Minor indentation adjustments made.
.github/workflows/release-dispatch.yml	Updated image version for propose-release job.

Possibly related PRs

• Update devcontainer image: v1.0.0-alpha.11 #2403: Updates the Docker image version to v1.0.0-alpha.11, related to the main PR's versioning.
• Update devcontainer image: v1.0.0-alpha.12 #2437: Updates the Docker image version to v1.0.0-alpha.12, showing progression in versioning.
• Update devcontainer image: v1.0.0-alpha.13 #2480: Updates the Docker image version to v1.0.0-alpha.13, continuing the versioning sequence.
• Update devcontainer image: v1.0.0-alpha.14 #2497: Updates the Docker image version to v1.0.0-alpha.14, the immediate predecessor to the current version.
• Prepare release: v1.0.0-alpha.15 #2511: Prepares for the release of version v1.0.0-alpha.15, indicating a direct relationship to this PR.

Suggested reviewers

• glihm

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between f56c4f9 and d4420c4.

📒 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)

✅ Files skipped from review due to trivial changes (1)

• .devcontainer/devcontainer.json

🧰 Additional context used

🔇 Additional comments (11)

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

17-17: Ohayo, sensei! The image update looks good!

The Docker image version has been successfully updated to v1.0.0-alpha.15. This change should provide the latest environment for the propose-release job.

Let's ensure this update is consistent across other workflow files, sensei:

✅ Verification successful

Ohayo, sensei! The Docker image version is consistent across all workflow files.

Everything looks good! The image update to v1.0.0-alpha.15 has been uniformly applied.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for consistency of Docker image version across workflow files

# Test: Search for the Docker image version in all workflow files
rg --type yaml 'ghcr.io/dojoengine/dojo-dev:v1\.0\.0-alpha\.\d+' .github/workflows/

Length of output: 1007

.github/workflows/bench.yml (2)

39-39: Ohayo again, sensei! The Docker image update is consistent!

The Docker image version has been updated to v1.0.0-alpha.15 in the bench-sozo job as well. This change is consistent with the update made in the bench-katana job, which is excellent!

It's great to see that both benchmarking jobs are using the same updated image version. This consistency helps maintain parity between the two benchmarks and ensures that any improvements or fixes in the new image version are applied across both jobs.

---

17-17: Ohayo, sensei! The Docker image update looks good!

The Docker image version has been bumped from v1.0.0-alpha.14 to v1.0.0-alpha.15. This update seems to be a minor version increment, which typically includes bug fixes or small improvements.

To ensure the new image works as expected, please run the following script:

.github/workflows/ci.yml (8)

58-58: Ohayo again, sensei! The ensure-wasm job's image update is on point.

The Docker image for the ensure-wasm job has been correctly updated to v1.0.0-alpha.15, maintaining consistency with the PR objective and the test job update.

---

123-123: Ohayo once more, sensei! The dojo-core-test job is following suit nicely.

The Docker image for the dojo-core-test job has been properly updated to v1.0.0-alpha.15, maintaining consistency across the workflow.

---

138-138: Ohayo yet again, sensei! The dojo-spawn-and-move-example-test job is in harmony.

The Docker image for the dojo-spawn-and-move-example-test job has been correctly updated to v1.0.0-alpha.15, maintaining the rhythm of updates across the workflow.

---

152-152: Ohayo, sensei! The dojo-world-bindings-check job is keeping up the pace.

The Docker image for the dojo-world-bindings-check job has been diligently updated to v1.0.0-alpha.15, maintaining the consistency we've seen so far.

---

161-161: Ohayo again, sensei! The clippy job is following the update pattern.

The Docker image for the clippy job has been updated to v1.0.0-alpha.15, maintaining the consistency we've observed throughout the workflow.

---

170-170: Ohayo once more, sensei! The fmt job is in perfect alignment.

The Docker image for the fmt job has been updated to v1.0.0-alpha.15, continuing the consistent pattern of updates across the workflow.

---

179-179: Ohayo for the last time, sensei! The docs job completes our update journey.

The Docker image for the docs job has been updated to v1.0.0-alpha.15, bringing our update saga to a satisfying conclusion.

Overall, all jobs in the CI workflow have been consistently updated to use the new Docker image version v1.0.0-alpha.15. This change aligns perfectly with the PR objective of updating the devcontainer image.

---

34-34: Ohayo, sensei! The Docker image update looks good.

The Docker image version has been successfully updated to v1.0.0-alpha.15 for the test job. This change aligns with the PR objective.

To ensure the new image is working as expected, please run the following script:

---

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 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 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.