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.5 #2774

Merged
merged 1 commit into from
Dec 6, 2024
Merged

Prepare release: v1.0.5 #2774

merged 1 commit into from
Dec 6, 2024

Conversation

tarrencev
Copy link
Contributor

@tarrencev tarrencev commented Dec 6, 2024

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

  • New Features

    • Updated workspace and package versions to 1.0.5, ensuring users have access to the latest features and improvements.
  • Bug Fixes

    • No specific bug fixes were mentioned, but the version updates may include various underlying improvements.
  • Documentation

    • Updated versioning documentation across multiple configuration files for clarity and consistency.

Copy link

coderabbitai bot commented Dec 6, 2024

Walkthrough

Ohayo, sensei! The pull request primarily involves version updates across multiple Scarb.toml files and the Cargo.toml file, changing the version from 1.0.4 to 1.0.5. This ensures that the workspace and its components are aligned with the latest versioning. Dependencies remain largely unchanged, with a focus on maintaining a structured dependency management system.

Changes

File Change Summary
Cargo.toml Version updated from 1.0.4 to 1.0.5.
crates/dojo/core/Scarb.toml Version updated from 1.0.4 to 1.0.5.
crates/torii/types-test/Scarb.toml Version updated from 1.0.4 to 1.0.5.
examples/spawn-and-move/Scarb.toml Version updated from 1.0.4 to 1.0.5.

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)

Ohayo sensei! Time to update that git dependency! 🎯

The crate ipfs-api-backend-hyper is available on crates.io with version 0.6.0, while the project is currently using a git dependency with a specific commit. You can replace the git dependency with the published version:

ipfs-api-backend-hyper = { version = "0.6.0", features = ["with-hyper-rustls", "with-send-sync"] }
🔗 Analysis chain

Line range hint 251-252: TODO comment needs attention, sensei! 🤔

There's a TODO comment regarding the git version of ipfs-api-backend-hyper. Consider evaluating if the git dependency is still necessary or if we can switch to a published version.

Let's check if there's a published version available:

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for published versions of ipfs-api-backend-hyper

# Check crates.io for published versions
curl -s https://crates.io/api/v1/crates/ipfs-api-backend-hyper | jq '.crate.max_version'

Length of output: 96


Script:

#!/bin/bash
# Let's check the actual dependency in Cargo.toml to see if it's using git
rg "ipfs-api-backend-hyper" -A 2 Cargo.toml

Length of output: 249

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between b821845 and a217d78.

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

62-62: Ohayo sensei! Version bump looks good! 🎉

The version update from 1.0.4 to 1.0.5 aligns with the release preparation objective.

Copy link

codecov bot commented Dec 6, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 56.02%. Comparing base (b821845) to head (a217d78).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2774   +/-   ##
=======================================
  Coverage   56.01%   56.02%           
=======================================
  Files         434      434           
  Lines       55068    55068           
=======================================
+ Hits        30847    30851    +4     
+ Misses      24221    24217    -4     

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

@glihm glihm merged commit c5e7d6b into main Dec 6, 2024
14 checks passed
@glihm glihm deleted the prepare-release branch December 6, 2024 00:42
@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