chore(devcontainer): update image: v1.0.7

[tarrencev]

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

• New Features

  • Updated Docker image version to v1.0.7 across various development and CI workflows.

• Bug Fixes

  • Improved consistency and reliability of the development environment and CI jobs with the newer Docker image.

[coderabbitai]

Walkthrough

Ohayo, sensei! This pull request updates the Docker image version across several configuration files related to a Rust development environment. Specifically, the image version has been incremented from v1.0.6 to v1.0.7 in the .devcontainer/devcontainer.json, .github/workflows/bench.yml, .github/workflows/ci.yml, and .github/workflows/release-dispatch.yml files. No other changes to the configuration settings or workflow structures were made in these files.

Changes

File Path	Change Summary
.devcontainer/devcontainer.json	Updated image version from v1.0.6 to v1.0.7.
.github/workflows/bench.yml	Updated image version from v1.0.6 to v1.0.7 in jobs bench-katana and bench-sozo.
.github/workflows/ci.yml	Updated image version from v1.0.6 to v1.0.7 in jobs test, ensure-wasm, dojo-core-test, dojo-spawn-and-move-example-test, clippy, fmt, docs.
.github/workflows/release-dispatch.yml	Updated image version from v1.0.6 to v1.0.7 in job propose-release.

Possibly related PRs

• 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, similar to the main PR's update from v1.0.6 to v1.0.7.
• Update devcontainer image: v1.0.0-alpha.14 #2497: Updates the Docker image version in .devcontainer/devcontainer.json from v1.0.0-alpha.13 to v1.0.0-alpha.14, continuing the pattern of version updates.
• Update devcontainer image: v1.0.0-alpha.16 #2535: Updates the Docker image version in .devcontainer/devcontainer.json from v1.0.0-alpha.15 to v1.0.0-alpha.16, maintaining the same context of version increments.
• Update devcontainer image: v1.0.0-alpha.17 #2559: Updates the Docker image version in .devcontainer/devcontainer.json from v1.0.0-alpha.16 to v1.0.0-alpha.17, consistent with the main PR's version update.
• Update devcontainer image: v1.0.0-rc.0 #2584: Updates the Docker image version in .devcontainer/devcontainer.json from v1.0.0-alpha.17 to v1.0.0-rc.0, showing a progression in versioning.
• Update devcontainer image: v1.0.0-rc.1 #2616: Updates the Docker image version in .devcontainer/devcontainer.json from v1.0.0-rc.0 to v1.0.0-rc.1, continuing the version update trend.
• Update devcontainer image: v1.0.0-rc.2 #2671: Updates the Docker image version in .devcontainer/devcontainer.json from v1.0.0-rc.1 to v1.0.0-rc.2, reflecting the same type of change as the main PR.
• Update devcontainer image: v1.0.0 #2678: Updates the Docker image version in .devcontainer/devcontainer.json from v1.0.0-rc.2 to v1.0.0, indicating a transition to a stable version.
• Update devcontainer image: v1.0.1 #2694: Updates the Docker image version in .devcontainer/devcontainer.json from v1.0.0 to v1.0.1, consistent with the main PR's version update.
• Update devcontainer image: v1.0.2 #2723: Updates the Docker image version in .devcontainer/devcontainer.json from v1.0.1 to v1.0.2, following the same pattern of version increments.
• chore(devcontainer): update image: v1.0.3 #2736: Updates the Docker image version in .devcontainer/devcontainer.json from v1.0.2 to v1.0.3, continuing the version update trend.
• chore(devcontainer): update image: v1.0.4 #2758: Updates the Docker image version in .devcontainer/devcontainer.json from v1.0.3 to v1.0.4, reflecting the same type of change as the main PR.
• chore(devcontainer): update image: v1.0.5 #2775: Updates the Docker image version in .devcontainer/devcontainer.json from v1.0.4 to v1.0.5, consistent with the main PR's version update.
• chore(devcontainer): update image: v1.0.6 #2802: Updates the Docker image version in .devcontainer/devcontainer.json from v1.0.5 to v1.0.6, following the same pattern of version increments.

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 180c6d2 and 639d3fd.

📒 Files selected for processing (4)

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

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

• .github/workflows/ci.yml
• .devcontainer/devcontainer.json
• .github/workflows/release-dispatch.yml

🔇 Additional comments (2)

.github/workflows/bench.yml (2)

17-17: LGTM! Container image version update looks good

The version bump from v1.0.6 to v1.0.7 is consistent across both benchmark jobs. This minor version update should maintain backward compatibility while providing improvements.

Also applies to: 39-39

---

17-17: Verify the new container image version

Ohayo sensei! Let's verify that the new image version exists and is properly tagged.

Also applies to: 39-39

---

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 generate docstrings to generate docstrings for this PR. (Experiment)
• @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 55.73%. Comparing base (180c6d2) to head (639d3fd).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2806   +/-   ##
=======================================
  Coverage   55.73%   55.73%           
=======================================
  Files         439      439           
  Lines       55613    55613           
=======================================
  Hits        30997    30997           
  Misses      24616    24616           

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