fix: wire up SKIP_ENV_VALIDATION in web env config

The t3-oss env validation was ignoring SKIP_ENV_VALIDATION because
skipValidation wasn't passed to createEnv. This broke CI builds
that don't have secrets available.

Author: akhileshrangani4

.github/workflows/ci.yml

@@ -69,6 +69,13 @@ jobs:
         run: npm run build
         env:
           SKIP_ENV_VALIDATION: "true"
+          GITHUB_CLIENT_ID: "dummy"
+          GITHUB_CLIENT_SECRET: "dummy"
+          E2B_API_KEY: "dummy"
+          CLERK_SECRET_KEY: "sk_test_dummy"
+          NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY: "pk_test_dGVuZGVyLWhvbmV5YmVlLTU2LmNsZXJrLmFjY291bnRzLmRldiQ"
+          NEXT_PUBLIC_APP_URL: "http://localhost:3000"
+          DATABASE_URL: "postgresql://dummy:dummy@localhost:5432/dummy"
 
   e2e:
     runs-on: ubuntu-latest

web/lib/env.ts

@@ -2,6 +2,7 @@ import { createEnv } from "@t3-oss/env-nextjs"
 import { z } from "zod"
 
 export const env = createEnv({
+  skipValidation: process.env.SKIP_ENV_VALIDATION === "true",
   server: {
     GITHUB_CLIENT_ID: z.string().min(1),
     GITHUB_CLIENT_SECRET: z.string().min(1),