Hello,
I would like to ask for some help understanding why the deployment_url sometimes returns different links in GitHub Actions. Let me explain.
I’m currently using Playwright for automated tests, and I configured the tests to use the VERCEL_AUTOMATION_BYPASS_SECRET (as per these instructions), and also configured GitHub actions to check the deployment_status (as per these instructions.
When the tests are triggered in GitHub, I noticed two different patterns (printing the variable) depending on the execution:
-
deployment_url: https://<company_domain>-bcnxcs6xu-<company_domain>-com.vercel.app/ (no staging in the URL). In this case, I have no problems with the tests.
-
deployment_url: https://<company_domain>-staging-bcnxcs6xu-<company_domain>-com.vercel.app/ (contains staging in the URL). In this case, the tests fail when trying to bypass the protection, regardless if bypass secret is set. The same problem happens when I try to run the tests locally.
I would like to know if there’s a logic in which “staging” is appended to the URL. And do you have any idea or advice as to how I can always get the version without staging, where the tests work as expected?
Thank you.