Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prepare release: v1.0.3 #2735

Merged
merged 1 commit into from
Nov 29, 2024
Merged

Prepare release: v1.0.3 #2735

merged 1 commit into from
Nov 29, 2024

Conversation

tarrencev
Copy link
Contributor

@tarrencev tarrencev commented Nov 28, 2024

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

  • New Features

    • No new features introduced in this release.
  • Updates

    • Incremented package version from 1.0.2 to 1.0.3 across multiple components.
    • Added a new dependency (slot) sourced from a Git repository.
  • Bug Fixes

    • Minor improvements and bug fixes implied with the version update.
  • Chores

    • Formatting adjustments in Cargo.toml files, including the addition of newline characters.

Copy link

coderabbitai bot commented Nov 29, 2024

Walkthrough

Ohayo, sensei! This pull request introduces updates primarily focused on versioning and dependency management across several Cargo.toml and Scarb.toml files. The workspace package version has been incremented from 1.0.2 to 1.0.3, and a new dependency, slot, has been added from a Git repository. Other packages also reflect the version update, while one file includes a minor formatting change. Overall, these modifications enhance the organization of dependencies without altering existing functionality.

Changes

File Path Change Summary
Cargo.toml - Version updated to 1.0.3
- Added dependency slot from Git repository
crates/dojo/core/Scarb.toml - Version updated to 1.0.3
crates/dojo/types/Cargo.toml - Added newline at the end of the file
crates/torii/types-test/Scarb.toml - Version updated to 1.0.3
examples/spawn-and-move/Scarb.toml - Version updated to 1.0.3

Possibly related PRs

Suggested reviewers

  • glihm

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

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (1)
Cargo.toml (1)

Line range hint 273-273: Consider using full git revision for slot dependency, sensei!

While pinning to a specific git revision is good practice, using a short revision (1298a30) could potentially lead to ambiguity if multiple commits share the same prefix. Consider using the full SHA-1 hash for better reproducibility.

-slot = { git = "https://github.com/cartridge-gg/slot", rev = "1298a30" }
+slot = { git = "https://github.com/cartridge-gg/slot", rev = "1298a30..." }  # Replace with full SHA-1
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between fe5c48e and 348b40b.

⛔ 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 (5)
  • Cargo.toml (1 hunks)
  • crates/dojo/core/Scarb.toml (1 hunks)
  • crates/dojo/types/Cargo.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)
  • crates/dojo/core/Scarb.toml
  • crates/dojo/types/Cargo.toml
  • crates/torii/types-test/Scarb.toml
  • examples/spawn-and-move/Scarb.toml
🔇 Additional comments (2)
Cargo.toml (2)

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

The version increment from 1.0.2 to 1.0.3 follows semantic versioning and aligns with the release preparation.


Line range hint 248-249: Ohayo! Let's verify the IPFS dependency requirement, sensei!

There's an unresolved TODO about checking if the git version of ipfs-api-backend-hyper is still needed. Consider verifying if:

  1. The published crate version now includes the required features
  2. The custom git dependency is still necessary
✅ Verification successful

Ohayo! The git dependency is still necessary, sensei!

After checking the published version (0.6.0) and comparing it with the git dependency, it appears the custom git version is still required because:

  • The project uses specific features (with-hyper-rustls, with-send-sync) in the workspace
  • The git dependency is referenced with a specific commit (af2c17f7b19ef5b9898f458d97a90055c3605633)
  • Multiple crates in the workspace depend on this specific version with custom features

The TODO can be resolved by keeping the git dependency as it's actively used across the codebase with specific feature requirements.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check latest published version and features
curl -s https://crates.io/api/v1/crates/ipfs-api-backend-hyper | jq -r '.crate.max_version, .crate.features'

Length of output: 121


Script:

#!/bin/bash
# Let's check the actual dependency in Cargo.toml
rg "ipfs-api-backend-hyper" -A 3 -B 3

# Also check for any TODO comments related to this dependency
rg -i "todo.*ipfs" 

Length of output: 3320

Copy link

codecov bot commented Nov 29, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 56.47%. Comparing base (fe5c48e) to head (348b40b).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2735      +/-   ##
==========================================
- Coverage   56.48%   56.47%   -0.02%     
==========================================
  Files         421      421              
  Lines       53976    53976              
==========================================
- Hits        30488    30482       -6     
- Misses      23488    23494       +6     

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

@glihm glihm merged commit c65c257 into main Nov 29, 2024
13 of 14 checks passed
@glihm glihm deleted the prepare-release branch November 29, 2024 00:17
@coderabbitai coderabbitai bot mentioned this pull request Dec 3, 2024
augustin-v pushed a commit to augustin-v/dojo that referenced this pull request Dec 4, 2024
@coderabbitai coderabbitai bot mentioned this pull request Dec 13, 2024
@coderabbitai coderabbitai bot mentioned this pull request Dec 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants