chore: add dojo 1.7.0

[kariy]

Summary by CodeRabbit

• Chores
  • Added availability of pre-release versions 1.7.0-alpha.0 and 1.7.0-alpha.1.
  • Defined compatibility: katana supports both 1.7.0-alpha.0 and 1.7.0-alpha.1; torii supports 1.7.0-alpha.0.
  • No changes or removals to existing versions; only new entries added.
  • These versions are now selectable wherever versioned components are configured or installed.

[coderabbitai]

Ohayo, sensei!

Walkthrough

Added two new top-level versions to versions.json: 1.7.0-alpha.0 and 1.7.0-alpha.1, each specifying dependency arrays for katana and torii. No existing entries were changed or removed.

Changes

Cohort / File(s)	Summary
Version registry updates versions.json	Added entries for "1.7.0-alpha.0" and "1.7.0-alpha.1": katana -> ["1.7.0-alpha.0","1.7.0-alpha.1"]; torii -> ["1.7.0-alpha.0"]. No modifications to existing mappings.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested reviewers

• glihm

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch addversion

---

🪧 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.
  • 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.
• 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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.

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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

🧹 Nitpick comments (1)

versions.json (1)

169-174: Order katana versions latest-first for consistency

Existing entries list compatible versions in descending (newest → oldest) order. Example: Lines 121-128 and 145-152. For consistency, consider listing alpha.1 before alpha.0.

Apply this diff to both katana arrays:

-    "katana": ["1.7.0-alpha.0", "1.7.0-alpha.1"],
+    "katana": ["1.7.0-alpha.1", "1.7.0-alpha.0"],

📜 Review details

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

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 89e31b7 and 1bc620f.

📒 Files selected for processing (1)

• versions.json (1 hunks)

🔇 Additional comments (2)

versions.json (2)

167-175: Ohayo, sensei! LGTM: valid JSON and consistent structure

The new 1.7.0 alpha entries are well-formed JSON, follow the existing schema, and fit the pattern of version-to-component compatibility maps.

---

170-174: ohayo sensei!

No action needed: torii version pin is correct

Verified via GitHub API that the v1.7.0-alpha.1 tag does not exist for dojoengine/torii, so keeping both entries pinned to 1.7.0-alpha.0 is intentional.