fix: bump version

[ponderingdemocritus]

• bumps version

Summary by CodeRabbit

• New Features

  • Updated CI workflow to reflect a transition from an alpha release to a release candidate version, indicating improved software stability.

• Chores

  • Changed the subproject commit reference to include the latest updates and improvements.

[coderabbitai]

Walkthrough

The changes in this pull request primarily involve updates to the GitHub Actions CI workflow and a subproject reference. The CI workflow in .github/workflows/ci.yaml has been modified to update the dojoup tool version from v1.0.0-alpha.17 to v1.0.0-rc.0, indicating a transition to a release candidate. Additionally, a commit reference in the worlds/dojo-starter subproject has been updated to a new commit. Commented-out lines related to coverage reporting in the CI workflow remain for potential future use.

Changes

File	Change Summary
.github/workflows/ci.yaml	Updated dojoup version from v1.0.0-alpha.17 to v1.0.0-rc.0; commented-out Codecov coverage upload lines remain.
worlds/dojo-starter	Updated subproject commit reference from 8e84a8b62815... to 4964f2b38671....

Possibly related PRs

• fix: entity sync #252: This PR updates the version of the dojoup command in the CI workflow file, similar to the main PR which also modifies the version parameter for dojoup.
• fix: submodule #272: This PR also updates the version of the dojoup command in the CI workflow file, indicating a related change in the same context as the main PR.
• feat: Torii upgrade #303: This PR continues the trend of updating the dojoup command version in the CI workflow file, showing a direct connection to the versioning changes made in the main PR.

🐰 In the garden of code, I hop with glee,
A version update, oh what a spree!
From alpha to RC, we leap and bound,
With changes so bright, new commits abound.
Let's celebrate progress, with carrots in tow,
For in the world of code, we continue to grow! 🌱

---

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.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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]

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (1)

.github/workflows/ci.yaml (1)

Line range hint 38-41: Consider enabling code coverage reporting

The commented-out Codecov configuration suggests incomplete coverage reporting setup. This could be valuable for maintaining code quality.

Would you like help setting up the Codecov integration? I can assist with:

1. Configuring the coverage reporting
2. Creating a codecov.yml configuration file
3. Documenting the setup process

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 8efc276 and 58e301f.

📒 Files selected for processing (2)

• .github/workflows/ci.yaml (1 hunks)
• worlds/dojo-starter (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• worlds/dojo-starter

🔇 Additional comments (1)

.github/workflows/ci.yaml (1)

23-23: Verify compatibility with dojoup v1.0.0-rc.0

The transition from alpha to release candidate version is significant. While this indicates improved stability, please ensure this RC version has been tested with your build process.

✅ Verification successful

Version update to dojoup v1.0.0-rc.0 appears stable and safe to use

The release candidate version shows:

• No reported issues specific to v1.0.0-rc.0
• Official release with stable builds for multiple platforms
• Contains mostly improvements and fixes without breaking changes
• Successfully transitioned from alpha to RC status through proper release process

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check if there are any reported issues with this RC version
gh issue list -R dojoengine/dojo --search "v1.0.0-rc.0"

# Check release notes/changelog for breaking changes
gh release view v1.0.0-rc.0 -R dojoengine/dojo

Length of output: 1198