chore(ComfyUI|Text Generation WebUI): update @super-protocol/solution-utils@1.4.0, @super-protocol/sdk-js@3.0.5, @super-protocol/dto-js@1.0.0

[DmitrySmv]

Summary by CodeRabbit

• Dependencies
  • Updated @super-protocol/solution-utils to version 1.4.0
  • Added new dependencies: @super-protocol/dto-js (v1.0.0) and @super-protocol/sdk-js (v3.0.5)
  • Applied consistent library updates across ComfyUI and Text Generation WebUI projects

[coderabbitai]

Walkthrough

The pull request involves updating dependencies across two different projects: ComfyUI and Text Generation WebUI. The changes focus on upgrading three specific Super Protocol libraries - solution-utils, dto-js, and sdk-js - to their latest versions. These updates suggest improvements in library functionality and potential compatibility enhancements across the projects.

Changes

File	Changes
ComfyUI/package.json	- Updated @super-protocol/solution-utils to 1.4.0 - Added @super-protocol/dto-js@1.0.0 - Added @super-protocol/sdk-js@3.0.5
Text Generation WebUI/package.json	- Updated @super-protocol/dto-js from 0.1.11 to 1.0.0 - Updated @super-protocol/sdk-js from 2.3.0 to 3.0.5 - Updated @super-protocol/solution-utils from 1.3.5 to 1.4.0

Poem

🐰 Hop, hop, dependencies dance!
Libraries leap to a newer stance
Version numbers climb so bright
Super Protocol's code takes flight
Upgrades sparkle with pure delight! 🚀

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2a8e411 and c00ed40.

⛔ Files ignored due to path filters (2)

• ComfyUI/package-lock.json is excluded by !**/package-lock.json
• Text Generation WebUI/package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (2)

• ComfyUI/package.json (1 hunks)
• Text Generation WebUI/package.json (1 hunks)

🔇 Additional comments (3)

ComfyUI/package.json (1)

26-28: Verify breaking changes in major version updates.

The changes include significant version updates and new dependencies:

• New dependency @super-protocol/dto-js@1.0.0
• New dependency @super-protocol/sdk-js@3.0.5
• Updated @super-protocol/solution-utils from 1.3.5 to 1.4.0

Let's check the changelog and migration guides for breaking changes:

✅ Verification successful

Dependencies verified and properly integrated

The dependencies are correctly used across multiple projects in the codebase, with no breaking changes detected in the version updates. The new dependencies serve specific purposes in the architecture and are properly integrated.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for breaking changes in the updated dependencies

# Fetch release notes and changelogs
echo "Checking @super-protocol/dto-js changelog..."
gh api repos/Super-Protocol/dto-js/releases/latest

echo "Checking @super-protocol/sdk-js changelog..."
gh api repos/Super-Protocol/sdk-js/releases/latest

echo "Checking @super-protocol/solution-utils changelog..."
gh api repos/Super-Protocol/solution-utils/releases/latest

Length of output: 4524

---

Script:

#!/bin/bash
# Search for usage of these packages and any related documentation
echo "Searching for imports and usage..."
rg "@super-protocol/(dto-js|sdk-js|solution-utils)" -A 2

echo -e "\nChecking for documentation..."
fd -g "README*" -X cat

Length of output: 67143

Text Generation WebUI/package.json (2)

27-29: Ensure version alignment with ComfyUI.

The dependency versions are now aligned with ComfyUI's package.json, which is good for maintaining consistency across projects.

---

27-29: Review impact of major version upgrades.

The changes include significant version jumps that may introduce breaking changes:

• @super-protocol/dto-js: 0.1.11 → 1.0.0 (major)
• @super-protocol/sdk-js: 2.3.0 → 3.0.5 (major)
• @super-protocol/solution-utils: 1.3.5 → 1.4.0 (minor)

Let's verify the dependency compatibility and check for any required code changes:

✅ Verification successful

Dependencies appear to be used safely ✅

The major version bumps in dto-js and sdk-js are transitive dependencies with no direct usage in the codebase. The only directly used package, solution-utils, has a backward-compatible minor version bump and is used only for stable configuration-related functionality.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Search for usage patterns that might be affected by breaking changes

# Search for dto-js usage patterns
echo "Checking @super-protocol/dto-js usage..."
rg -l "@super-protocol/dto-js"

# Search for sdk-js usage patterns
echo "Checking @super-protocol/sdk-js usage..."
rg -l "@super-protocol/sdk-js"

# Search for solution-utils usage patterns
echo "Checking @super-protocol/solution-utils usage..."
rg -l "@super-protocol/solution-utils"

Length of output: 2258

---

Script:

#!/bin/bash
# Check specific usage patterns in Text Generation WebUI

echo "Checking dto-js imports and usage in Text Generation WebUI..."
rg -A 2 "from '@super-protocol/dto-js'" "Text Generation WebUI"

echo -e "\nChecking sdk-js imports and usage in Text Generation WebUI..."
rg -A 2 "from '@super-protocol/sdk-js'" "Text Generation WebUI"

echo -e "\nChecking solution-utils usage in Text Generation WebUI..."
rg -A 2 "from '@super-protocol/solution-utils'" "Text Generation WebUI"

# Check package.json for previous versions
echo -e "\nChecking previous versions in package.json..."
git show HEAD^:Text\ Generation\ WebUI/package.json | grep -A 3 "@super-protocol"

Length of output: 1965

---

🪧 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 generate docstrings to generate docstrings for this PR. (Beta)
• @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.