Skip to content

Changelog

Changelog

Follow us on X to hear about the changes first!

@vercel/otel 1.3.0

Vercel and Next.js provide increased observability of your applications through OpenTelemetry.

instrumentation.ts
import { registerOTel } from '@vercel/otel';
export function register() {
registerOTel({ serviceName: 'acme-co' });
}
Using the Vercel OTEL package with Next.js.

v1.3.0 of @vercel/otel now providing custom resource and operation names for Datadog to satisfy their cardinality requirements. You can group related URL paths for a given span to reduce cardinality and associated usage.

For example, /products/hoodie can be mapped to /products/[name].

Learn more in our documentation or start using the package with Next.js.

No action required: Lowering default function timeout in new Enterprise projects

The default Vercel Function timeout of all new projects for Enterprise customers has been reduced to 15 seconds. This change helps prevent unintentional function usage, unless explicitly opted into the longer function duration (up to 15 minutes).

Existing Enterprise projects will not have their defaults changed.

Check out our documentation to learn more.

Cover for UTM parameter support in Web AnalyticsCover for UTM parameter support in Web Analytics

UTM parameter support in Web Analytics

UTM parameters are now available in Vercel Web Analytics, enabling detailed insights into marketing campaign effectiveness directly from the dashboard.

  • Visibility into campaign performance: Analyze traffic by specific campaigns, mediums, sources, content, and terms using UTM parameters.
  • Advanced filtering: Apply filters based on UTM parameters for deeper insights into the impact of your marketing campaigns.
  • Historical UTM data: Start analyzing past campaigns immediately with historical data automatically included.

This feature is available to Pro customers with Web Analytics Plus and Enterprise customers.

Cover for AI Integration and playground in the Vercel DashboardCover for AI Integration and playground in the Vercel Dashboard

AI Integration and playground in the Vercel Dashboard

You can now incorporate AI models and services from industry-leading providers into your Vercel projects with a single click.

  • AI tab: Seamlessly integrate with 3rd-party AI providers and vector databases.
  • Playground: In-dashboard playground to explore and experiment with models and preview their outputs.

Check out the documentation to get started.

Cover for Recent Preview Deployments now displayed in the dashboardCover for Recent Preview Deployments now displayed in the dashboard

Recent Preview Deployments now displayed in the dashboard

Preview deployments you have recently viewed or deployed are now accessible from the Recent Previews column on your dashboard.

Each recent preview includes a link to the deployment's page in Vercel and a link to the PR or source on your git provider's site when available.

Learn more in the dashboard overview documentation.

Invite collaborators to view and comment on your deployments

You can now invite emails or team members to view a deployment through the share menu. All invitees will receive an email with a link to the deployment and have access to comment if comments are enabled.

The share menu will display who currently has access to a given deployment. Users with sufficient permissions will also be able to revoke access.

Visit the documentation to learn more about all options for sharing deployments.

Legacy environment variable secrets are being sunset

Legacy secrets are being sunset in favor of Sensitive Environment Variables, which are now shareable across projects.

  • Existing legacy secrets will be automatically converted. You do not need to manually take action for non-development values. Read below to view your impacted projects.
  • All Environment Variables remain securely encrypted. The majority of Vercel workloads have moved from the legacy secrets functionality.

On May 1st, 2024 secrets will be automatically converted to sensitive Environment Variables for Preview and Production environments. Secrets attached to Development environments will not be migrated.

Why are legacy secrets being sunset?

Our legacy secrets were encrypted values global for your entire team and could only be managed through the CLI. Based on your feedback, we have since:

When will I no longer be able to use secrets?

On May 1st, 2024secrets will be removed from Vercel CLI:

  • Existing secrets added to the Preview and Production environments will be converted to Sensitive Environment Variables
  • Existing secrets added to the Development environment will not be migrated for your security. If you have a secret shared between all environments, including Development, it will not be migrated. These values must be manually migrated.

How can I migrate to Sensitive Environment Variables?

Secrets for Preview and Production environments will be automatically migrated.

For secrets which contain the Development environment, you should create new Sensitive Environment Variables, as these values will not be automatically migrated for your security. If you need to share Environment Variables across projects, you can make them shared.

How can I understand if I’m affected?

To list projects using secrets that will be automatically converted, run:

Terminal
vercel secrets ls
View the secrets added to your Vercel teams.

Cover for Sensitive environment variables are now availableCover for Sensitive environment variables are now available

Sensitive environment variables are now available

You can now add sensitive Environment Variables to your projects for added security of secret values like API keys.

While all Environment Variables are encrypted, sensitive values can only be decrypted during builds. This replaces our legacy secrets implementation which is being sunset.

Get started using Sensitive Environment Variables through the dashboard or with Vercel CLI 33.4.

Cover for Switch between branches directly from deploymentsCover for Switch between branches directly from deployments

Switch between branches directly from deployments

You can now switch between branches directly from the Vercel Toolbar.

Access the command menu through the toolbar or ⌘K (Ctrl+K on Windows) and select branch switcher. You’ll see your team’s branches sorted to highlight those with recent activity or unread comments. Then, select a branch to switch to that deployment.

Learn more about the command menu and other features of the toolbar.

Instrument and trace applications with the OpenTelemetry collector

Vercel and Next.js provide increased observability of your applications through OpenTelemetry.

instrumentation.ts
import { registerOTel } from '@vercel/otel';
export function register() {
registerOTel({ serviceName: 'acme-co' });
}
Using the Vercel OTEL package with Next.js.

v1.0 of @vercel/otel now supports:

  • Support for Node.js and Edge runtimes
  • Telemetry context propagation, including W3C Trace Context
  • Fetch API instrumentation with context propagation
  • Support and auto-configuration for the Vercel OTEL collector
  • Enhanced metadata reporting
  • Sampling support
  • Custom tracing exporter support
  • Batched trace exporting

Learn more in our documentation or start using the package with Next.js.

Vercel and Next.js provide increased observability of your applications through OpenTelemetry.

instrumentation.ts
import { registerOTel } from '@vercel/otel';
export function register() {
registerOTel({ serviceName: 'acme-co' });
}
Using the Vercel OTEL package with Next.js.

v1.3.0 of @vercel/otel now providing custom resource and operation names for Datadog to satisfy their cardinality requirements. You can group related URL paths for a given span to reduce cardinality and associated usage.

For example, /products/hoodie can be mapped to /products/[name].

Learn more in our documentation or start using the package with Next.js.

The default Vercel Function timeout of all new projects for Enterprise customers has been reduced to 15 seconds. This change helps prevent unintentional function usage, unless explicitly opted into the longer function duration (up to 15 minutes).

Existing Enterprise projects will not have their defaults changed.

Check out our documentation to learn more.

Cover for UTM parameter support in Web AnalyticsCover for UTM parameter support in Web Analytics

UTM parameters are now available in Vercel Web Analytics, enabling detailed insights into marketing campaign effectiveness directly from the dashboard.

  • Visibility into campaign performance: Analyze traffic by specific campaigns, mediums, sources, content, and terms using UTM parameters.
  • Advanced filtering: Apply filters based on UTM parameters for deeper insights into the impact of your marketing campaigns.
  • Historical UTM data: Start analyzing past campaigns immediately with historical data automatically included.

This feature is available to Pro customers with Web Analytics Plus and Enterprise customers.

Cover for AI Integration and playground in the Vercel DashboardCover for AI Integration and playground in the Vercel Dashboard

You can now incorporate AI models and services from industry-leading providers into your Vercel projects with a single click.

  • AI tab: Seamlessly integrate with 3rd-party AI providers and vector databases.
  • Playground: In-dashboard playground to explore and experiment with models and preview their outputs.

Check out the documentation to get started.

Cover for Recent Preview Deployments now displayed in the dashboardCover for Recent Preview Deployments now displayed in the dashboard

Preview deployments you have recently viewed or deployed are now accessible from the Recent Previews column on your dashboard.

Each recent preview includes a link to the deployment's page in Vercel and a link to the PR or source on your git provider's site when available.

Learn more in the dashboard overview documentation.

You can now invite emails or team members to view a deployment through the share menu. All invitees will receive an email with a link to the deployment and have access to comment if comments are enabled.

The share menu will display who currently has access to a given deployment. Users with sufficient permissions will also be able to revoke access.

Visit the documentation to learn more about all options for sharing deployments.

Legacy secrets are being sunset in favor of Sensitive Environment Variables, which are now shareable across projects.

  • Existing legacy secrets will be automatically converted. You do not need to manually take action for non-development values. Read below to view your impacted projects.
  • All Environment Variables remain securely encrypted. The majority of Vercel workloads have moved from the legacy secrets functionality.

On May 1st, 2024 secrets will be automatically converted to sensitive Environment Variables for Preview and Production environments. Secrets attached to Development environments will not be migrated.

Why are legacy secrets being sunset?

Our legacy secrets were encrypted values global for your entire team and could only be managed through the CLI. Based on your feedback, we have since:

When will I no longer be able to use secrets?

On May 1st, 2024secrets will be removed from Vercel CLI:

  • Existing secrets added to the Preview and Production environments will be converted to Sensitive Environment Variables
  • Existing secrets added to the Development environment will not be migrated for your security. If you have a secret shared between all environments, including Development, it will not be migrated. These values must be manually migrated.

How can I migrate to Sensitive Environment Variables?

Secrets for Preview and Production environments will be automatically migrated.

For secrets which contain the Development environment, you should create new Sensitive Environment Variables, as these values will not be automatically migrated for your security. If you need to share Environment Variables across projects, you can make them shared.

How can I understand if I’m affected?

To list projects using secrets that will be automatically converted, run:

Terminal
vercel secrets ls
View the secrets added to your Vercel teams.

Cover for Sensitive environment variables are now availableCover for Sensitive environment variables are now available

You can now add sensitive Environment Variables to your projects for added security of secret values like API keys.

While all Environment Variables are encrypted, sensitive values can only be decrypted during builds. This replaces our legacy secrets implementation which is being sunset.

Get started using Sensitive Environment Variables through the dashboard or with Vercel CLI 33.4.

Cover for Switch between branches directly from deploymentsCover for Switch between branches directly from deployments

You can now switch between branches directly from the Vercel Toolbar.

Access the command menu through the toolbar or ⌘K (Ctrl+K on Windows) and select branch switcher. You’ll see your team’s branches sorted to highlight those with recent activity or unread comments. Then, select a branch to switch to that deployment.

Learn more about the command menu and other features of the toolbar.

Vercel and Next.js provide increased observability of your applications through OpenTelemetry.

instrumentation.ts
import { registerOTel } from '@vercel/otel';
export function register() {
registerOTel({ serviceName: 'acme-co' });
}
Using the Vercel OTEL package with Next.js.

v1.0 of @vercel/otel now supports:

  • Support for Node.js and Edge runtimes
  • Telemetry context propagation, including W3C Trace Context
  • Fetch API instrumentation with context propagation
  • Support and auto-configuration for the Vercel OTEL collector
  • Enhanced metadata reporting
  • Sampling support
  • Custom tracing exporter support
  • Batched trace exporting

Learn more in our documentation or start using the package with Next.js.