Prepare release: v1.0.1

[tarrencev]

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

• New Features

  • Incremented version numbers for multiple packages to 1.0.1, reflecting minor updates.

• Bug Fixes

  • No bug fixes were introduced in this release, but the version updates may include underlying improvements in dependencies.

[coderabbitai]

Walkthrough

Ohayo, sensei! This pull request introduces version updates across multiple Scarb.toml files and the Cargo.toml file. The workspace version in Cargo.toml has been incremented from 1.0.0 to 1.0.1, and similar updates have been made to the version fields in the Scarb.toml files for various packages. No changes to dependencies or project structure are present, focusing solely on version increments.

Changes

File	Change Summary
Cargo.toml	Updated workspace version from 1.0.0 to 1.0.1.
crates/dojo/core/Scarb.toml	Updated package version from 1.0.0 to 1.0.1.
crates/torii/types-test/Scarb.toml	Updated package version from 1.0.0 to 1.0.1.
examples/spawn-and-move/Scarb.toml	Updated package version from 1.0.0 to 1.0.1.

Possibly related PRs

• Prepare release: v1.0.0 #2676: The changes in this PR involve updating the version in Cargo.toml from 1.0.0-rc.2 to 1.0.0, which is directly related to the version update in the main PR that increments the workspace version from 1.0.0 to 1.0.1.
• Prepare release: v1.0.0 #2676: Similar to the main PR, this PR also updates the version in Scarb.toml files for various packages, indicating a consistent versioning approach across the project.

Suggested reviewers

• glihm

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between fac5a67 and 602ef71.

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

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

---

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 56.34%. Comparing base (fac5a67) to head (602ef71).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2693      +/-   ##
==========================================
- Coverage   56.35%   56.34%   -0.01%     
==========================================
  Files         411      411              
  Lines       52742    52742              
==========================================
- Hits        29723    29719       -4     
- Misses      23019    23023       +4     

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