Update devcontainer image: v1.0.0-alpha.14

[tarrencev]

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

• New Features

  • Updated Docker image version to v1.0.0-alpha.14 across various development and CI workflows, enhancing the development environment and benchmarking processes.

• Bug Fixes

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

These changes aim to ensure a more stable and efficient development experience.

[coderabbitai]

Walkthrough

Ohayo, sensei! This pull request updates the Docker image version across several configuration files related to a Rust development environment and GitHub Actions workflows. Specifically, the image version is changed from v1.0.0-alpha.13 to v1.0.0-alpha.14 in .devcontainer/devcontainer.json, multiple jobs in .github/workflows/ci.yml, and several other workflow files. The structure and logic of the workflows remain unchanged, focusing solely on the image version upgrade.

Changes

File Path	Change Summary
.devcontainer/devcontainer.json	Updated Docker image version from v1.0.0-alpha.13 to v1.0.0-alpha.14.
.github/workflows/bench.yml	Updated Docker image version from v1.0.0-alpha.13 to v1.0.0-alpha.14 in jobs bench-katana and bench-sozo.
.github/workflows/ci.yml	Updated Docker image version from v1.0.0-alpha.13 to v1.0.0-alpha.14 in 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 Docker image version from v1.0.0-alpha.13 to v1.0.0-alpha.14 in propose-release job.

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.
• Update devcontainer image: v1.0.0-alpha.12 #2437: Updates the Docker image version in .devcontainer/devcontainer.json from v1.0.0-alpha.11 to v1.0.0-alpha.12.
• Update devcontainer image: v1.0.0-alpha.13 #2480: Updates the Docker image version in .devcontainer/devcontainer.json from v1.0.0-alpha.12 to v1.0.0-alpha.13.
• Prepare release: v1.0.0-alpha.14 #2496: Prepares for the release of version 1.0.0-alpha.14, aligning with the main PR's update.

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 6bafcb5 and 3e2525a.

📒 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 comments (11)

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

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

The Docker image version has been bumped from v1.0.0-alpha.13 to v1.0.0-alpha.14. This change keeps our development environment up-to-date, which is totally sugoi!

Let's make sure this new image version is used consistently across the project, sensei. Here's a quick check:

✅ Verification successful

Ohayo, sensei! It looks like the new Docker image version isn't referenced elsewhere in the project. Let's gather more information to ensure it's used consistently across all necessary areas:

---

Ohayo, sensei! It seems there was a hiccup with our previous script. Let's fix that and ensure we're accurately checking the Docker image references:

---

Ohayo, sensei! 🎉

The Docker image has been successfully updated to v1.0.0-alpha.14 across all relevant workflow files. No references to the old version remain, ensuring consistency throughout the project.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for consistent use of the new Docker image version

# Test: Search for any remaining references to the old version
rg 'ghcr.io/dojoengine/dojo-dev:v1.0.0-alpha.13'

# Test: Confirm the new version is used where expected
rg 'ghcr.io/dojoengine/dojo-dev:v1.0.0-alpha.14'

Length of output: 97

---

Script:

#!/bin/bash
# Description: List all files that reference any Docker images

fd --type f --hidden --exclude-dir=node_modules --exclude-dir=dist --exclude-dir=build -e yml -e yaml -e dockerfile -e docker-compose -e js -e ts . | xargs rg 'ghcr.io/dojoengine/dojo-dev'

# Description: Check if the new Docker image version is referenced correctly
rg 'ghcr.io/dojoengine/dojo-dev:v1.0.0-alpha.14'

Length of output: 471

---

Script:

#!/bin/bash
# Description: List all files that reference any Docker images

fd --type f --hidden --exclude node_modules --exclude dist --exclude build -e yml -e yaml -e dockerfile -e docker-compose -e js -e ts . | xargs rg 'ghcr.io/dojoengine/dojo-dev'

# Description: Check if the new Docker image version is referenced correctly
rg 'ghcr.io/dojoengine/dojo-dev:v1.0.0-alpha.14'

Length of output: 1542

.github/workflows/bench.yml (2)

39-39: Ohayo again, sensei! This change is also on point!

The Docker image version has been updated to v1.0.0-alpha.14 for the bench-sozo job as well. It's great to see consistency between both jobs.

---

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

The Docker image version has been bumped to v1.0.0-alpha.14. This aligns with the PR objective.

To ensure compatibility, please run the following script:

.github/workflows/ci.yml (8)

34-34: Ohayo, image update looks good, sensei!

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

---

58-58: Ohayo, another smooth image update, sensei!

The Docker image for the ensure-wasm job has been correctly updated to v1.0.0-alpha.14. This change maintains consistency with the other updates in this PR.

---

123-123: Ohayo, sensei! The image update train keeps rolling!

The dojo-core-test job is now using the latest v1.0.0-alpha.14 image. This change aligns perfectly with the other updates in this PR.

---

138-138: Ohayo! Another flawless image update, sensei!

The dojo-spawn-and-move-example-test job has been successfully updated to use the v1.0.0-alpha.14 image. This change maintains the consistency of the updates across the workflow.

---

152-152: Ohayo, sensei! The image update saga continues!

The dojo-world-bindings-check job is now equipped with the latest v1.0.0-alpha.14 image. This change keeps the workflow in perfect harmony with the other updates.

---

161-161: Ohayo! The clippy job joins the image update party, sensei!

The clippy job has been successfully updated to use the v1.0.0-alpha.14 image. This change ensures that the linting process is using the latest development environment.

---

170-170: Ohayo, sensei! The fmt job gets a shiny new image too!

The fmt job has been updated to use the v1.0.0-alpha.14 image. This change ensures that the formatting checks are performed using the latest development environment.

---

179-179: Ohayo, sensei! The grand finale of image updates!

The docs job has been successfully updated to use the v1.0.0-alpha.14 image. This change completes the set of updates across all jobs in the workflow.

To summarize the overall impact:

1. All jobs using the dojo-dev image have been consistently updated to version v1.0.0-alpha.14.
2. These updates ensure that all CI/CD processes are using the latest development environment.
3. The changes are uniform and maintain consistency across the entire workflow.

Great job on keeping the CI/CD pipeline up-to-date, sensei!

---

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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 68.96%. Comparing base (6bafcb5) to head (3e2525a).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2497   +/-   ##
=======================================
  Coverage   68.95%   68.96%           
=======================================
  Files         372      372           
  Lines       48568    48568           
=======================================
+ Hits        33492    33496    +4     
+ Misses      15076    15072    -4     

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