Skip to content

chore(versions): torii 1.5.6 - #3237

Closed
Larkooo wants to merge 1 commit into
mainfrom
Larkooo-patch-3
Closed

chore(versions): torii 1.5.6#3237
Larkooo wants to merge 1 commit into
mainfrom
Larkooo-patch-3

Conversation

@Larkooo

@Larkooo Larkooo commented Jun 4, 2025

Copy link
Copy Markdown
Collaborator

Summary by CodeRabbit

  • Chores
    • Updated the version list for the "torii" component to include the latest release, "1.5.6".

@coderabbitai

coderabbitai Bot commented Jun 4, 2025

Copy link
Copy Markdown
Contributor

Walkthrough

Ohayo sensei! This change updates the versions.json file by adding "1.5.6" as the newest version for the "torii" component, placing it at the beginning of the version list while retaining the previous versions in order.

Changes

File(s) Change Summary
versions.json Prepended "1.5.6" to the "torii" component's version list.

Possibly related PRs

Suggested reviewers

  • kariy
  • steebchen

🪧 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 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 8b03eef and 8d525d3.

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

Comment thread versions.json
"1.5.1": {
"katana": ["1.5.3", "1.5.2", "1.5.1", "1.5.0"],
"torii": ["1.5.5", "1.5.4", "1.5.3", "1.5.2", "1.5.1", "1.5.0"]
"torii": ["1.5.6", "1.5.5", "1.5.4", "1.5.3", "1.5.2", "1.5.1", "1.5.0"]

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

❓ Verification inconclusive

ohayo sensei! Torii bump looks correct.

The new "1.5.6" entry is appropriately prepended in descending order, matching the existing pattern.

Sensei check: verify that 1.5.6 is published in the registry.


🏁 Script executed:

#!/usr/bin/env bash
# Verify torii 1.5.6 exists in the registry
npm view torii@1.5.6 version

Length of output: 401


Torii version “1.5.6” not published

Ohayo sensei! I ran the verification command and received a 404 for npm view torii@1.5.6 version, so version 1.5.6 isn’t available in the npm registry yet. Please publish the release or update versions.json to an existing version before merging.

• File: versions.json
• Line: 20 – the newly added "1.5.6" entry

🤖 Prompt for AI Agents
In versions.json at line 20, the newly added version "1.5.6" for torii is not
published in the npm registry, causing a 404 error on verification. Remove
"1.5.6" from the list or replace it with the latest published version available
in the registry before merging to ensure the versions.json only references
valid, published versions.

@glihm

glihm commented Jun 11, 2025

Copy link
Copy Markdown
Contributor

Sorry didn't see that before adding it directly. Thanks mate.

@glihm glihm closed this Jun 11, 2025
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.

2 participants