Bump Orca / Stonfi deps

[0xh3rman]

No description provided.

[semanticdiff-com]

Review changes with  

Changed Files

File	Status
packages/swapper/package.json	83% smaller
package.json	60% smaller
apps/api/src/index.ts	29% smaller
pnpm-lock.yaml	13% smaller
.gitignore	Unsupported file format
apps/api/tsconfig.json	0% smaller
packages/swapper/src/stonfi/integration.test.ts	0% smaller
packages/swapper/src/stonfi/testkit.ts	0% smaller
scripts/generate-version.js	0% smaller

[gemini-code-assist]

Summary of Changes

Hello @0xh3rman, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request primarily focuses on updating critical dependencies for Orca and Stonfi within the swapper package to ensure compatibility and leverage the latest features and fixes. Alongside these updates, a comprehensive suite of integration tests has been introduced for the Stonfi provider, significantly enhancing test coverage and reliability for TON-based swaps.

Highlights

• Dependency Updates: Key dependencies including @orca-so/whirlpools, @orca-so/whirlpools-client, @ston-fi/api, and @ton/ton have been updated to their latest versions, ensuring compatibility and leveraging new features.
• Stonfi Integration Tests: New integration tests have been added for the Stonfi provider, covering various swap scenarios such as TON to USDT, USDT to TON, and Jetton to Jetton swaps, enhancing test coverage and reliability.
• Stonfi Test Utilities: Dedicated utility functions and asset definitions for Stonfi testing have been introduced, streamlining the creation and management of test cases.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates several dependencies, including major version bumps for @orca-so/whirlpools (v5 to v6) and various @solana/* packages. While new integration tests have been added for the Stonfi provider, which is excellent, there are no corresponding tests for the Orca provider. Major version updates often introduce breaking changes, and merging this without verifying the Orca integration is risky and could break functionality in production. This is a critical issue. I strongly recommend adding integration tests for the Orca provider to ensure it works correctly with the new dependencies before this PR is merged.

I've also left a couple of comments on the new test files with suggestions for improving code clarity and maintainability.