Prepare release: v1.0.0-alpha.19

[tarrencev]

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

• New Features
  • Updated workspace version to 1.0.0-alpha.19, indicating progress in development.
• Dependency Management
  • Specified dependencies with updated versions to ensure compatibility and functionality across the project.

[coderabbitai]

Walkthrough

Ohayo, sensei! The changes in this pull request involve updates to the Cargo.toml file, primarily focusing on version management and dependency specifications. The workspace version has been incremented from 1.0.0-alpha.18 to 1.0.0-alpha.19. Dependencies have been organized, with specific versions and features outlined, including updates for cairo-lang to version 2.7.0. The project maintains a structured approach to managing its components through these modifications.

Changes

File	Change Summary
Cargo.toml	- Version updated from 1.0.0-alpha.18 to 1.0.0-alpha.19
	- Specified cainome dependency with git repository and tag
	- Maintained paths for dependencies: dojo-utils, dojo-bindgen, dojo-core, dojo-lang, dojo-test-utils, dojo-types, dojo-world
	- Updated cairo-lang dependency to version 2.7.0
	- Specified versions and features for dependencies like tokio, tonic, and serde

Possibly related PRs

• Prepare release: v1.0.0-alpha.18 #2576: The changes in this PR involve updating the version in Cargo.toml from 1.0.0-alpha.17 to 1.0.0-alpha.18, which is directly related to the version update in the main PR from 1.0.0-alpha.18 to 1.0.0-alpha.19.

Suggested reviewers

• glihm

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 51b0297 and cbfce95.

⛔ Files ignored due to path filters (1)

• Cargo.lock is excluded by !**/*.lock

📒 Files selected for processing (1)

• Cargo.toml (1 hunks)

🔇 Additional comments (2)

Cargo.toml (2)

56-56: Ohayo sensei! Version bump looks good!

The version update to 1.0.0-alpha.19 aligns perfectly with our release preparation objectives.

---

Line range hint 1-250: Ohayo sensei! Dependencies are well-organized, but let's verify version consistency.

The dependency organization looks excellent with clear grouping and specific versions. Notably, all cairo-lang dependencies are consistently at version 2.7.0, which is properly aligned with Scarb's version.

Let's verify that all cairo-lang related dependencies are consistently versioned:

✅ Verification successful

Ohayo sensei! All cairo-lang dependencies are perfectly aligned at version 2.7.0 🎯

The verification shows complete version consistency:

• All cairo-lang dependencies in the root Cargo.toml are at version 2.7.0
• All cairo-lang dependencies in katana/cairo/Cargo.toml are also at version 2.7.0
• This aligns perfectly with the Scarb dependency at tag v2.7.0

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify cairo-lang dependency versions are consistent
# Expected: All cairo-lang dependencies should be at version 2.7.0

echo "Checking cairo-lang dependency versions..."
rg "cairo-lang-.*= \"([^\"]+)\"" -o | sort | uniq -c

Length of output: 1747

---

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 69.57%. Comparing base (51b0297) to head (cbfce95).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2583      +/-   ##
==========================================
- Coverage   69.67%   69.57%   -0.10%     
==========================================
  Files         401      401              
  Lines       50818    50848      +30     
==========================================
- Hits        35405    35378      -27     
- Misses      15413    15470      +57     

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