Update devcontainer image: v1.0.0-alpha.8

[tarrencev]

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

• New Features
  • Updated Docker image version to enhance the development environment across multiple workflows.
• Bug Fixes
  • Upgraded to a newer Docker image version, which may include various bug fixes and improvements.
• Chores
  • Consistent updates to the Docker image version in workflow configurations for better performance and functionality.

[coderabbitai]

Walkthrough

Ohayo, sensei! The changes involve an update to the Docker image version across various configuration files for a Rust development environment. The image has been upgraded from v1.0.0-alpha.7 to v1.0.0-alpha.8 in the .devcontainer/devcontainer.json, .github/workflows/bench.yml, .github/workflows/ci.yml, and .github/workflows/release-dispatch.yml files. Additionally, several Rust files have had the #[allow(clippy::too_long_first_doc_paragraph)] attribute added to suppress linting warnings related to documentation formatting.

Changes

Files	Change Summary
.devcontainer/devcontainer.json, .github/workflows/bench.yml, .github/workflows/ci.yml, .github/workflows/release-dispatch.yml	Updated Docker image version from ghcr.io/dojoengine/dojo-dev:v1.0.0-alpha.7 to ghcr.io/dojoengine/dojo-dev:v1.0.0-alpha.8.
crates/dojo-utils/src/tx/waiter.rs, crates/dojo-world/src/config/profile_config.rs, crates/katana/tasks/src/lib.rs, crates/sozo/ops/src/model.rs	Added #[allow(clippy::too_long_first_doc_paragraph)] attribute to suppress linting warnings in documentation comments.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant DevContainer
    participant GitHubActions

    User->>DevContainer: Pull image v1.0.0-alpha.8
    DevContainer->>User: Development environment ready
    User->>GitHubActions: Trigger workflow
    GitHubActions->>GitHubActions: Use image v1.0.0-alpha.8 for jobs
    GitHubActions->>User: Workflow completed

Loading

---

Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 6ca0db0 and 18043d2.

Files selected for processing (4)

• crates/dojo-utils/src/tx/waiter.rs (1 hunks)
• crates/dojo-world/src/config/profile_config.rs (1 hunks)
• crates/katana/tasks/src/lib.rs (1 hunks)
• crates/sozo/ops/src/model.rs (1 hunks)

Files skipped from review due to trivial changes (4)

• crates/dojo-utils/src/tx/waiter.rs
• crates/dojo-world/src/config/profile_config.rs
• crates/katana/tasks/src/lib.rs
• crates/sozo/ops/src/model.rs

---

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>.
  • 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 show all the console.log statements in this repository.
  • @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 as 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.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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 67.51%. Comparing base (d31f81e) to head (18043d2).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2356   +/-   ##
=======================================
  Coverage   67.51%   67.51%           
=======================================
  Files         359      359           
  Lines       46955    46955           
=======================================
  Hits        31704    31704           
  Misses      15251    15251           

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