-
Notifications
You must be signed in to change notification settings - Fork 433
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update default value for Relay Service URL #2488
Update default value for Relay Service URL #2488
Conversation
CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Should we update prod as well?
I was waiting for a confirmation on the production URLs but it seems that they can be updated as well. Do you prefer a separate PR or should I include the update on this one? |
This one pls |
Updates the default value set for `SAFE_RELAY_SERVICE_URL_STAGING` from `https://safe-client-nest.staging.5afe.dev/v1/relay` to `https://safe-client.staging.5afe.dev/v1/relay`
Updates the default value set for `NEXT_PUBLIC_SAFE_RELAY_SERVICE_URL_PRODUCTION` from `https://safe-client-nest.safe.global/v1/relay` to `https://safe-client.safe.global/v1/relay`
9805da6
to
03163bb
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you sir.
What it solves
The
-nest
name in the domain name should not be used anymore and will be removed in the future. This PR updates the respective value to use the new supported URL.How this PR fixes it
SAFE_RELAY_SERVICE_URL_STAGING
fromhttps://safe-client-nest.staging.5afe.dev/v1/relay
tohttps://safe-client.staging.5afe.dev/v1/relay
SAFE_RELAY_SERVICE_URL_PRODUCTION
fromhttps://safe-client-nest.safe.global/v1/relay
tohttps://safe-client.safe.global/v1/relay
How to test it
NA
Screenshots
NA
Checklist