SKIP_EMAIL_VERIFICATION_IN_DEV Usage in Pipeline

I am working on creating a pipeline to run some e2e-tests where I set the

SKIP_EMAIL_VERIFICATION_IN_DEV

SKIP_EMAIL_VERIFICATION_IN_DEV

variable to

true

true

. When I run the tests locally, this variable behaves as expected where the set user doesn't need to verify their email. When I run the same tests within a bitbucket pipeline the tests are getting snagged on logging in requiring verification despite the variable being set.
After reviewing the docs I see that there is specific mention of "development mode" for the usage of this variable so i'm curious if there's more to that definition? Has anyone else ran into this or has any ideas on how to get this variable to behave as expected in a bitbucket pipeline?