Skip to content

chore: add Katana 1.6.2 - #3280

Merged
kariy merged 1 commit into
mainfrom
updatekatana
Jul 11, 2025
Merged

chore: add Katana 1.6.2#3280
kariy merged 1 commit into
mainfrom
updatekatana

Conversation

@kariy

@kariy kariy commented Jul 11, 2025

Copy link
Copy Markdown
Member

Summary by CodeRabbit

  • Chores
    • Updated version lists to include the latest "katana" version (1.6.2) as the newest available option.

@coderabbitai

coderabbitai Bot commented Jul 11, 2025

Copy link
Copy Markdown
Contributor

Walkthrough

Ohayo sensei! This update modifies the versions.json file by prepending the new "1.6.2" version to the "katana" component arrays for the "1.6.0-alpha.0", "1.6.0-alpha.1", and "1.6.0-alpha.2" keys. No other files or components are changed.

Changes

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

Possibly related PRs

Suggested reviewers

  • steebchen
✨ 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.

@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: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between bb88f9f and 6dbb43e.

📒 Files selected for processing (1)
  • versions.json (3 hunks)

Comment thread versions.json
Comment on lines 32 to 34
"1.6.0-alpha.0": {
"katana": ["1.6.1", "1.6.0", "1.6.0-alpha.1", "1.6.0-alpha.0"],
"katana": ["1.6.2", "1.6.1", "1.6.0", "1.6.0-alpha.1", "1.6.0-alpha.0"],
"torii": [

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.

💡 Verification agent

🧩 Analysis chain

Ohayo sensei! Verify that Katana 1.6.2 is published and no duplicate slips in
Great to see the latest patch added, but before merge please double-check that:

  1. The katana 1.6.2 artifact is actually available in the registry you deploy from.
  2. Each list remains de-duplicated and ordered newest → oldest.

You can run this quick sanity script from the repo root:

Also applies to: 48-49, 63-64


🏁 Script executed:

#!/bin/bash
# Validate availability (replace the URL/tool if you host Katana elsewhere)
curl -sfI "https://pypi.org/pypi/katana/1.6.2/json" || {
  echo "❌ katana 1.6.2 not found on PyPI"; exit 1;
}

# Detect accidental duplicates across the three updated arrays
jq '
  ["1.6.0-alpha.0","1.6.0-alpha.1","1.6.0-alpha.2"]
  | map(.[].katana) as $lists
  | ($lists | flatten) as $all
  | if ($all | unique | length) != ($all | length)
       then "❌ duplicate katana versions detected"
       else "✅ no duplicates"
    end' versions.json

Length of output: 3020


❌ Ohayo sensei! Katana 1.6.2 isn’t published on PyPI yet – please publish before merging

It looks like our sanity check failed:

  • curl -sfI https://pypi.org/pypi/katana/1.6.2/json returns 404
  • The duplicate-check script didn’t run because we exited early

Please address the following before we can approve:

• Publish the Katana 1.6.2 artifact to your registry (e.g. PyPI).

curl -sfI https://pypi.org/pypi/katana/1.6.2/json \
  && echo "✅ katana 1.6.2 is live" \
  || { echo "❌ katana 1.6.2 not found – publish it first"; exit 1; }

• Re-run the duplicate-detection across all version arrays to ensure no slipped-in duplicates and that lists remain sorted newest→oldest.

Once Katana 1.6.2 is live and there are no duplicates, we’re good to merge!

🤖 Prompt for AI Agents
In versions.json around lines 32 to 34, the version "1.6.2" of Katana is listed
but not yet published on PyPI, causing a 404 error during the sanity check.
First, publish the Katana 1.6.2 artifact to PyPI or your package registry. After
confirming it is live by checking the URL, re-run the duplicate detection script
on all version arrays to ensure there are no duplicates and that the versions
are sorted from newest to oldest before merging.

@kariy
kariy merged commit acb476a into main Jul 11, 2025
1 check passed
@kariy
kariy deleted the updatekatana branch July 11, 2025 14:07
@coderabbitai coderabbitai Bot mentioned this pull request Jul 18, 2025
10 tasks
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.

1 participant