Prepare release: v1.4.1

[tarrencev]

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

• Chores
  • Updated version numbers from 1.4.0 to 1.4.1 across multiple package configuration files.
  • Added a missing newline at the end of a configuration file for improved formatting.

[coderabbitai]

Walkthrough

Ohayo sensei! This update consists of version number increments from 1.4.0 to 1.4.1 across several manifest files (Cargo.toml and Scarb.toml) within the project, as well as the addition of a missing newline at the end of one manifest. No changes were made to dependencies, code, features, or configuration beyond these version bumps.

Changes

File(s)	Change Summary
Cargo.toml	Updated [workspace.package] version to 1.4.1
bin/torii/Cargo.toml	Added missing newline at end of file
crates/dojo/core/Scarb.toml crates/torii/types-test/Scarb.toml examples/spawn-and-move/Scarb.toml	Updated package version to 1.4.1
crates/macros/merge-options/macro_test/Cargo.toml	Updated package version to 1.4.1

Possibly related PRs

• Prepare release: v1.0.4 #2756: Also bumps version numbers in the same manifest files without other changes.
• Prepare release: v1.0.11 #2908: Performs a similar version number update in the same set of files.
• Prepare release: v1.2.1 #3046: Updates version numbers in Cargo.toml and Scarb.toml files for a new release.

Suggested reviewers

• glihm

Tip

⚡💬 Agentic Chat (Pro Plan, General Availability)

• We're introducing multi-step agentic chat in review comments and issue comments, within and outside of PR's. This feature enhances review and issue discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments and add commits to existing pull requests.

---

📜 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 2a00600 and ee5c92c.

⛔ 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)
• bin/torii/Cargo.toml (1 hunks)
• crates/dojo/core/Scarb.toml (1 hunks)
• crates/macros/merge-options/macro_test/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)

bin/torii/Cargo.toml (1)

13-14: Ohayo sensei! Added newline at EOF—nice attention to detail.

This change aligns with best practices for file formatting and improves compatibility with various tools. No issues here!

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

3-3: Ohayo sensei! Version bump looks perfect.

The update to 1.4.1 is consistent with the rest of the workspace. All good!

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

4-4: Ohayo sensei! Version updated smoothly.

The version bump to 1.4.1 is spot on and matches the release prep across the repo.

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

5-5: Ohayo sensei! Version bump is clean and consistent.

No issues—this keeps everything in sync for the release.

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

6-6: Ohayo sensei! Version bump to 1.4.1 is perfect.

Everything is in order for the release. No concerns here!

Cargo.toml (1)

64-64: Ohayo sensei! Version bump looks perfect.

The update from 1.4.0 to 1.4.1 is spot on for release prep. No issues found—let's ship it! 🚀

---

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 55.62%. Comparing base (2a00600) to head (ee5c92c).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3163   +/-   ##
=======================================
  Coverage   55.62%   55.62%           
=======================================
  Files         443      443           
  Lines       62987    62987           
=======================================
  Hits        35034    35034           
  Misses      27953    27953           

☔ 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.