You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: replace amondnet/vercel-action with direct Vercel CLI steps
Root cause: YAML >- block scalar joins lines with a space, so multi-word
values like 'Freelance DevOps & Cloud Engineering' passed as --build-env
flags were word-split by the shell — 'DevOps' became a bare token that
Vercel CLI treated as a file/directory path.
Fix: drop amondnet/vercel-action + vercel-args entirely. Use direct
'run:' steps with the official Vercel CLI instead:
1. Install vercel@latest globally
2. Write .env.production via heredoc (no shell-splitting — values with
spaces, ampersands, etc. are safe)
3. vercel pull --yes --environment=production (creates .vercel/ dir)
4. vercel env add RESEND_API_KEY production --force (server-only secret)
5. vercel build --prod (local build, reads .env.production)
6. vercel deploy --prebuilt --prod (upload artefact, no remote re-build)
.env.production is covered by '.env.*' in .gitignore so it is never
accidentally committed.
--build-env NEXT_PUBLIC_SITE_DESCRIPTION="I design, build, and operate cloud-native infrastructure. From Kubernetes to CI/CD pipelines, I help startups ship faster and stay reliable."
--build-env NEXT_PUBLIC_OWNER_BIO="I work directly with founders and engineering teams to design, automate, and stabilize cloud environments across AWS and Azure."
NEXT_PUBLIC_SITE_DESCRIPTION=I design, build, and operate cloud-native infrastructure. From Kubernetes to CI/CD pipelines, I help startups ship faster and stay reliable.
0 commit comments