chore: bump sor to 4.17.5 - fix: mixed route support v4 ETH pool to v2/v3 WETH pool new way #814
+414
−37
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…2/v3 WETH pool new way
This stack of pull requests is managed by Graphite. Learn more about stacking. |
|
Updated dependencies detected. Learn more about Socket for GitHub ↗︎
|
xrsv
reviewed
Jan 31, 2025
xrsv
reviewed
Jan 31, 2025
cgkol
approved these changes
Jan 31, 2025
jsy1218
deleted the
siyujiang/fix-mixed-route-v4-ETH-v2v3-WETH-new-way
branch
Graphite Automations"Request reviewers once CI passes on smart-order-router repo" took an action on this PR • (01/31/25)3 reviewers were added and 1 assignee was added to this PR based on Siyu Jiang (See-You John)'s automation. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
What is the current behavior? (You can also link to an open issue here)
What is the new behavior (if this is a feature change)?
Other information: