fix(tokens): use vault relayer address corr to env#7557
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
WalkthroughReformats ChangesFrontend import updates
ESLint import rules
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Deploying swap-dev with
|
| Latest commit: |
6584955
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://3f9d6e91.swap-dev-5u6.pages.dev |
| Branch Preview URL: | https://fix-approve-vault-staging.swap-dev-5u6.pages.dev |
|
In general it works. But what I notice is, if I give approval it doesn't (always) show the spinner and often just out of the blue, shows that is approved (with delay). Can this be addressed? Screencast_20260522_155531.webmOther automated Findings
|
fairlighteth
left a comment
There was a problem hiding this comment.
Added a few comments.
… fix/approve-vault-staging
|
@fairlighteth thanks!
|
Deploying explorer-dev with
|
| Latest commit: |
6584955
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://b7517c4f.explorer-dev-dxz.pages.dev |
| Branch Preview URL: | https://fix-approve-vault-staging.explorer-dev-dxz.pages.dev |


Summary
Approval flow doesn't work on the Tokens page on the staging environment.
The cause is that
COW_PROTOCOL_VAULT_RELAYER_ADDRESSfrom SDK is the prod address, but we shoud import it from@cowprotocol/common-utilsto have it environment dependent.p.s. there is existing eslint rule which is supposed to protect against similar issues, but it was not covering
cowswap-frontend.To Test
Summary by CodeRabbit
Refactor
Chores