feat: use latest test-tube

[gorgos]

Summary by CodeRabbit

• Chores
  • Updated internal dependencies to the latest versions.
  • Incremented the package version for injective-testing.

[coderabbitai]

Walkthrough

The changes update dependency and package versions in Cargo.toml files. Specifically, the injective-test-tube dependency is upgraded to a newer beta version, and the injective-testing package version is incremented. No code, configuration, or public API changes are present.

Changes

File(s)	Change Summary
Cargo.toml	Updated injective-test-tube dependency version.
packages/injective-testing/Cargo.toml	Bumped injective-testing package version.

Poem

A hop and a skip, new versions arrive,
Dependencies fresh, our code will thrive.
With numbers bumped and betas anew,
The garden of crates gets morning dew.
🐇✨

---

📜 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 22d8dfa and f1d1377.

⛔ Files ignored due to path filters (1)

• Cargo.lock is excluded by !**/*.lock

📒 Files selected for processing (2)

• Cargo.toml (1 hunks)
• packages/injective-testing/Cargo.toml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (3)

• GitHub Check: Test Suite
• GitHub Check: Lints
• GitHub Check: Test Suite

🔇 Additional comments (3)

packages/injective-testing/Cargo.toml (1)

8-8: Bump package version to 1.1.11.

Aligns the package version with the updated injective-test-tube dependency and downstream usage.

Cargo.toml (2)

23-23: Confirm injective-test-tube version bump to 1.16.0-beta.3.

The dependency was updated from 1.16.0-beta.2.1 to 1.16.0-beta.3; please verify compatibility and update any related lockfiles or documentation.

---

24-24: Sync workspace dependency for injective-testing.

The package in packages/injective-testing/Cargo.toml was bumped to 1.1.11; consider updating the workspace dependency here from 1.1.10 to 1.1.11 to maintain consistency.

---

🪧 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.

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.

[jbernal87]

LGTM