chore: add Katana 1.6.1

[kariy]

Description

Related issue

Tests

• Yes
• No, because they aren't needed
• No, because I need help

Added to documentation?

• README.md
• Dojo Book
• No documentation needed

Checklist

• I've formatted my code (scripts/rust_fmt.sh, scripts/cairo_fmt.sh)
• I've linted my code (scripts/clippy.sh, scripts/docs.sh)
• I've commented my code
• I've requested a review after addressing the comments

Summary by CodeRabbit

• Chores
  • Updated version listings for the "katana" component to prioritize version 1.6.1 in relevant version arrays.

[coderabbitai]

Walkthrough

Ohayo sensei! The change updates the "katana" version arrays in versions.json for the keys "1.6.0-alpha.0", "1.6.0-alpha.1", and "1.6.0-alpha.2", prepending "1.6.1" to each array. No other components or files were modified.

Changes

File(s)	Change Summary
versions.json	Prepended "1.6.1" to the "katana" version arrays for "1.6.0-alpha.0", "1.6.0-alpha.1", and "1.6.0-alpha.2". No other changes.

Possibly related PRs

• chore: add katana@1.5.3 #3230: Also modifies "katana" version arrays in versions.json by prepending new versions.
• chore: add katana 1.5.4 #3245: Updates "katana" version mappings in versions.json with new prepended versions.
• chore: add Katana 1.6.1 #3275: Makes similar changes to the same "katana" version arrays by adding "1.6.1" at the start.

Suggested reviewers

• glihm

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 1bdce55 and a033260.

📒 Files selected for processing (1)

• versions.json (3 hunks)

🔇 Additional comments (2)

versions.json (2)

32-34: Ohayo sensei! Katana 1.6.1 correctly prepended across alpha tracks – looks solid.

The new entry keeps the arrays in descending sem-ver order and avoids duplicates. No functional issues spotted here.

Also applies to: 48-49, 63-64

---

32-34: ohayo sensei!

Verify Katana 1.6.1 artifacts & CI compatibility

• Ran a scan for hard-coded katana:1.6.0 references outside of versions.json—no hits found.
• Please double-check that Docker images/tarballs for katana:1.6.1 are published to your registry.
• Ensure any downstream CI/CD jobs that consume versions.json will pick up the new 1.6.1 tag without issues.

✨ Finishing Touches

🧪 Generate unit tests

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

---

🪧 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

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

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 generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai auto-generate unit tests to generate unit tests 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.