Prepare release: v1.3.0

[tarrencev]

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

• Chores
  • Updated package versions to 1.3.0 across multiple components to reflect a new release.
• Style
  • Applied minor formatting improvements for consistency.

[coderabbitai]

Ohayo, sensei!

Walkthrough

This pull request updates the version numbers in several package configuration files. Most files now report a version change from "1.2.2" to "1.3.0", while one file updates from "0.1.0" to "1.3.0". Additionally, a minor formatting adjustment (adding a newline) was made in one Cargo.toml file. These changes adhere to semantic versioning and do not alter any functional logic.

Changes

Files	Change Summary
Cargo.toml, crates/dojo/core/Scarb.toml, crates/torii/types-test/Scarb.toml, examples/.../Scarb.toml	Package version updated from "1.2.2" to "1.3.0".
crates/macros/.../Cargo.toml	Package version updated from "0.1.0" to "1.3.0".
crates/torii/server/Cargo.toml	A newline was added at the end of the file (formatting only).

Possibly related PRs

• Prepare release: v0.7.3 #2133: Updates version numbers in Cargo.toml and Scarb.toml files for a new release increment.
• Prepare release: v1.0.8 #2813: Similar version update in the Scarb.toml file, reflecting the release version change.

Suggested reviewers

• glihm

Tip

⚡🧪 Multi-step agentic review comment chat (experimental)

• We're introducing multi-step agentic chat in review comments. This experimental feature enhances review discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments.
  - To enable this feature, set early_access to true under in the settings.

---

📜 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 fffa060 and 2785069.

⛔ 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 (6)

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

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

• GitHub Check: build

🔇 Additional comments (6)

crates/dojo/core/Scarb.toml (1)

6-6: Ohayo sensei, version update is solid!
The package version has been updated to "1.3.0", which aligns perfectly with our coordinated release strategy. Everything looks consistent here.

crates/torii/types-test/Scarb.toml (1)

5-5: Ohayo sensei, the version upgrade here looks perfect!
The version change to "1.3.0" is consistent with our other packages and follows our semantic versioning guidelines.

crates/macros/merge-options/macro_test/Cargo.toml (1)

3-3: Ohayo sensei, version update noted in the macro package.
Bumping the version from "0.1.0" to "1.3.0" marks a significant and appropriate leap, ensuring uniformity across our release. Just double-check that any dependent modules are aware of this upgrade.

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

4-4: Ohayo sensei, awesome version alignment!
Updating the version to "1.3.0" here keeps our examples in sync with the rest of our project. Great work ensuring consistency!

crates/torii/server/Cargo.toml (1)

39-41: Ohayo sensei, nice formatting fix!
The minor change—adding a newline and affirming that the "uuid" dependency remains at "1.15.1"—improves the file's clarity without impacting functionality.

Cargo.toml (1)

64-64: Version Bump Looks Solid, Sensei!
Ohayo sensei, the version field in [workspace.package] is updated to "1.3.0" as planned. This change is consistent with the coordinated release across the repository. Just double-check that all dependent packages or documentation referencing the version are updated accordingly.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
• @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.10%. Comparing base (fffa060) to head (2785069).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3106   +/-   ##
=======================================
  Coverage   57.10%   57.10%           
=======================================
  Files         442      442           
  Lines       61077    61077           
=======================================
+ Hits        34876    34877    +1     
+ Misses      26201    26200    -1     

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

🚀 New features to boost your workflow:

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.