As title says. I believe this is a quick fix in the azure-pipeline configs or on the Azure Dev Ops portal. Will look into it and follow up. cc @fastify/leads