Skip to content

Prepare release: v1.4.2 - #3176

Merged
glihm merged 1 commit into
mainfrom
prepare-release
Apr 17, 2025
Merged

Prepare release: v1.4.2#3176
glihm merged 1 commit into
mainfrom
prepare-release

Conversation

@tarrencev

@tarrencev tarrencev commented Apr 17, 2025

Copy link
Copy Markdown
Contributor

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

  • Chores
    • Updated package version numbers from 1.4.1 to 1.4.2 across multiple project manifest files. No functional changes were made.

@coderabbitai

coderabbitai Bot commented Apr 17, 2025

Copy link
Copy Markdown
Contributor

Walkthrough

Ohayo sensei! This pull request updates the version numbers from 1.4.1 to 1.4.2 across several manifest files in the project. The changes are limited to version bumps in Cargo.toml and Scarb.toml files for various packages and examples. No modifications were made to dependencies, configuration, code, or public entity declarations.

Changes

File(s) Change Summary
Cargo.toml Updated [workspace.package] version to 1.4.2
crates/dojo/core/Scarb.toml Updated package version to 1.4.2
crates/macros/merge-options/macro_test/Cargo.toml Updated package version to 1.4.2
crates/torii/types-test/Scarb.toml Updated package version to 1.4.2
examples/spawn-and-move/Scarb.toml Updated package version to 1.4.2

Possibly related PRs

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.

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

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
Cargo.toml (1)

64-64: Consider updating release notes or CHANGELOG.md.

Since we've bumped to 1.4.2, please ensure that the project’s CHANGELOG or release notes are updated to reflect any newly included fixes or features.

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 374fd38 and c5eabb7.

⛔ 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/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 (5)
crates/torii/types-test/Scarb.toml (1)

5-5: Ohayo sensei! Version bump looks good.

The version field has been updated from 1.4.1 to 1.4.2, keeping this manifest in sync with the workspace release.

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

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

The crate version has been correctly updated to 1.4.2 to align with the rest of the workspace.

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

4-4: Ohayo sensei! Version bump looks good.

The example’s version has been updated to 1.4.2, matching the core release.

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

6-6: Ohayo sensei! Version bump looks good.

The dojo core package version is now 1.4.2, in line with the new release.

Cargo.toml (1)

64-64: Ohayo sensei! Workspace version bump is correct.

The workspace package version has been updated to 1.4.2. Everything else remains unchanged.

@glihm glihm changed the title Prepare release: v Prepare release: v1.4.2 Apr 17, 2025
@glihm
glihm enabled auto-merge (squash) April 17, 2025 17:47
@glihm
glihm merged commit b5eabcf into main Apr 17, 2025
@glihm
glihm deleted the prepare-release branch April 17, 2025 18:07
@codecov

codecov Bot commented Apr 17, 2025

Copy link
Copy Markdown

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 55.61%. Comparing base (374fd38) to head (c5eabb7).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3176      +/-   ##
==========================================
- Coverage   55.63%   55.61%   -0.02%     
==========================================
  Files         443      443              
  Lines       62987    62987              
==========================================
- Hits        35043    35032      -11     
- Misses      27944    27955      +11     

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

kariy pushed a commit that referenced this pull request Apr 21, 2025
Prepare release: v

Co-authored-by: steebchen <steebchen@users.noreply.github.com>
kariy pushed a commit that referenced this pull request Apr 28, 2025
Prepare release: v

Co-authored-by: steebchen <steebchen@users.noreply.github.com>
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.

3 participants