Build logs now redact Sensitive Environment Variable values
Vercel now automatically redacts sensitive environment variable values in deployment build logs when marked as sensitive and 32 characters or longer, with visibility indicators showing when redaction occurred. The system also redacts selected system environment variables used for deployment security.
When an Environment Variable is marked Sensitive and has a value 32 characters or longer, Vercel now replaces it with in the deployment's build logs.[REDACTED]
The Build Logs view also indicates when redaction happened, giving teams visibility into why output was masked without ever exposing the underlying value. When a value is redacted, Vercel logs the Environment Variable key, project, and deployment in the Activity Log, but never the value.
Vercel also redacts selected system Environment Variables used for deployment security.
Learn more about .Sensitive Environment Variables
Source: original entry ↗
More from Vercel
Follow Vercel to get its new changes in your feed and email digest.
Skip sending request bodies to Routing Middleware
Vercel now allows you to skip sending client request bodies to Routing Middleware via the skipMiddlewareRequestBody configuration option, reducing middleware invocation costs and improving time to first byte for requests with large bodies.
Vercel Sandbox creation now returns ready sandbox
Vercel Sandbox instances are now ready to run commands and access files immediately upon creation completion. The Sandbox.create() method now waits for snapshot restoration to finish before resolving, eliminating delays on the first command or file operation.
Step 5 Preview now available on AI Gateway
StepFun's Step 5 Preview model is now available on Vercel's AI Gateway, supporting text and image input with a 1M-token context window optimized for agentic coding, professional knowledge work, and financial analysis. The model can be accessed via the unified AI Gateway API for tracking usage, cost management, and performance optimization.