Prepare release: v1.1.2

[tarrencev]

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

• Chores
  • Updated package version from 1.1.1 to 1.1.2 across multiple project configuration files
  • Version bump applies to Cargo.toml and Scarb.toml files in workspace, core, types-test, and example directories

[coderabbitai]

Walkthrough

Ohayo, sensei! This pull request involves a version increment from 1.1.1 to 1.1.2 across multiple configuration files in a Rust workspace. The update is consistent across the root Cargo.toml and several Scarb.toml files in different project directories, including core, types-test, and an example project. This appears to be a standard version bump to track the project's incremental release.

Changes

File	Change Summary
Cargo.toml	Version updated from 1.1.1 to 1.1.2 in workspace package
crates/dojo/core/Scarb.toml	Package version incremented from 1.1.1 to 1.1.2
crates/torii/types-test/Scarb.toml	Package version incremented from 1.1.1 to 1.1.2
examples/spawn-and-move/Scarb.toml	Package version incremented from 1.1.1 to 1.1.2

Possibly related PRs

• Prepare release: v1.1.1 #2963: Version updated from 1.1.0 to 1.1.1, indicating a similar version increment pattern
• Prepare release: v1.1.0 #2958: Version updated from 1.0.12 to 1.1.0, showing progression in versioning
• Prepare release: v1.0.12 #2915: Version updated from 1.0.11 to 1.0.12, part of the version increment history

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 38d22ac and 6b39e22.

⛔ Files ignored due to path filters (4)

• Cargo.lock is excluded by !**/*.lock
• crates/dojo/core/Scarb.lock is excluded by !**/*.lock
• crates/torii/types-test/Scarb.lock is excluded by !**/*.lock
• examples/spawn-and-move/Scarb.lock is excluded by !**/*.lock

📒 Files selected for processing (4)

• Cargo.toml (1 hunks)
• crates/dojo/core/Scarb.toml (1 hunks)
• crates/torii/types-test/Scarb.toml (1 hunks)
• examples/spawn-and-move/Scarb.toml (1 hunks)

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

• crates/dojo/core/Scarb.toml
• crates/torii/types-test/Scarb.toml
• Cargo.toml

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: fmt

🔇 Additional comments (1)

examples/spawn-and-move/Scarb.toml (1)

4-4: Ohayo sensei! Version bump looks consistent.

The version increment to 1.1.2 aligns with the coordinated update across the workspace.

Let's double-check the version consistency across all configuration files:

✅ Verification successful

Ohayo sensei! Version bump is perfectly synchronized! ✨

The version 1.1.2 is consistently set across all configuration files in the workspace, including:

• Main Cargo.toml
• Core Dojo Scarb.toml
• Torii types test Scarb.toml
• Spawn-and-move example Scarb.toml

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify version consistency across Cargo.toml and Scarb.toml files

echo "Checking Cargo.toml versions..."
rg -g 'Cargo.toml' 'version\s*=\s*"1\.1\.2"'

echo -e "\nChecking Scarb.toml versions..."
rg -g 'Scarb.toml' 'version\s*=\s*"1\.1\.2"'

Length of output: 489

---

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. (Beta)
• @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 57.19%. Comparing base (38d22ac) to head (6b39e22).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2970      +/-   ##
==========================================
- Coverage   57.20%   57.19%   -0.02%     
==========================================
  Files         423      423              
  Lines       56125    56125              
==========================================
- Hits        32107    32100       -7     
- Misses      24018    24025       +7     

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