Skip to content

Blog

At Next.js Conf, we announced Next.js Analytics, providing developers with their Real Experience Score through data from actual visitors. Today we're expanding Vercel's analytics offerings to include Gatsby.

Read more →

September 2020·Changelog
  • Dashboard
    • A new "Login Connections" page was added to the Personal Account Settings as a replacement for the "OAuth" page. It now renders all three Git providers instead of just GitHub.
    • The Project View now allows for jumping directly to the connected Git repository by clicking on its name. Previously, this forwarded users to the Project Settings.
    • Users that are entering the Project Creation Flow through a Deploy Button are now presented with a dedicated screen that explains what Vercel is and optionally renders a preview of the Git repository that they're about to deploy.
    • The "Visit" button on the Deployment View now correctly suggests deploying to the right Production Branch if no Production Deployment was created yet.
    • For failed Deployments, the "Redeploy" button on the Deployment View is now always visible, regardless of whether the Deployment was created via Git or not.
    • The pages of the Project Creation Flow will now always be visually attached to the top of the viewport instead of moving around whenever they're growing in height.
    • In the Project Settings, the banner that indicates that Environment Variables can now be configured on a dedicated page was removed for everyone.
    • The confirmation modals that are rendered after clicking the "Redeploy" or "Promote to Production" button now reliably render correct information.
    • Clicking "Promote to Production" will now cause helpful notifications to be rendered on the bottom right of the screen.
    • Losing your connection to the internet will no longer cause the Vercel Dashboard to crash. Instead, a notification will be rendered.
    • Clicking the "Back" button in the Project Creation Flow now works reliably.
    • Switching to a different Personal Account or Team now results in a good transition, regardless of which page you're looking at.
    • Queued Deployments will no longer render on the Deployment View that they're waiting for the Build to finish. Instead, they will now render that they're waiting for the Build to start.
    • It's not longer possible to redeploy a Production Deployment if a more recent one has been created. This ensures the most recent Production Deployment is never accidentally overwritten with old source code (only possible via explicit "Promote to Production").
    • Whenever a Deployment is automatically canceled by the Ignored Build Step feature, a helpful message is now rendered on the Deployment View.
    • The Deployment View will now render a helpful message whenever a Serverless Function exceeds the maximum unzipped Lambda size.
    • The button for removing Environment Variables in the Project Creation Flow can be clicked again.
    • Build Logs rendered on the Deployment View are now automatically cut off at 2,000 lines and a helpful message is displayed. This is to prevent the user's browser from running out of memory.
    • Creating a Deployment in the Project Creation Flow on a phone or tablet (small viewport) now reliably renders the Build Logs.
  • Deployments
    • Sending a request with a unsupported range within the Range header will now cause a helpful error to be returned (instead of a "Internal Server Error").
    • Using the functions property in vercel.json now works reliably with Next.js' Serverless Functions placed inside pages/api.
    • The 404 message that renders whenever a path on a Deployment couldn't be found doesn't render a banner anymore that shows that the Domain is available for use.
    • Clicking the Vercel logo on a public Deployment will no longer try to transition to the Dashboard of the owner of the Deployment. Instead, the Dashboard of the currently logged in user will be presented.
    • When using the functions property in vercel.json with Next.js, a warning will now be rendered if sub properties are used that are not supported by the framework.
  • Documentation
    • The URL fields on the Deploy Button page now allow for query string parameters to be placed within them.
    • A new Login Connections page was added under the "Platform" category.
    • The publicly available Git repository for the documentation was archived and moved to an internal location to allow for a better Engineering workflow.
    • New documentation sections about the Build Cache and Build Image were added.
    • For the routes property, the documentation now outlines that the new routing properties (rewrites, redirects, headers, cleanUrls, trailingSlash) should be used instead.
    • The Deploy Button page now contains new "Demo" sections, which talk about how to display a preview of a Git repository in the Project Creation Flow.
    • For the functions property, the documentation now clearly outlines which sub properties can be used in conjunction with the Next.js framework.
    • A new documentation section about Concurrent Builds was added.
  • Integrations
    • All Git Integrations (for GitHub, GitLab and Bitbucket) were completely revamped from the ground up to provide maximum reliability across all areas of the Git workflow.
    • Redeploying a Deployment or promoting it to Production will now update the status of the commit that it is associated with on the Git provider.
    • Deployments that need to be authorized by a Team Member because they were created in a pull request that originated on a fork (and the Deployment will receive Secrets) will now cause a comment to be rendered on the pull request.
    • The comment that is left on pull requests of Git repositories that are deployed to Vercel no longer shows "In Progress" for completed Deployments.
    • Deploy Hooks won't issue a Deployment for all Vercel Projects connected to a Git repository anymore. Only for the one they're configured on.
    • Deployments created through Deploy Hooks will now automatically be canceled if they're not the most recent one created by a specific Deploy Hook anymore.
    • Requesting access to a Team on Vercel when pushing a commit is now much 1.5s faster, as an artificial delay was removed.
    • Whenever the "Ignored Build Step" command causes a Deployment to be canceled, the Git Integrations will now render a clear message as the commit status.
    • Installing a Git Integration will now forward users to vercel.com instead of zeit.co for completing the installation.
  • Command-Line
    • The vercel dev command will no longer fail if the tsconfig.json file that is used contains comments (which is the case when running tsc --init, for example).
  • Other
    • A new Entity component was added to the design system, which allows for rendering a list of items in good-looking way.
    • Deleting a Team will no longer cause emails about failed payments to be sent to its owners if the Team was deleted during the trial phase.
    • Whenever a signup is deemed to potentially be malicious, the user is now required to verify their phone number via SMS before entering Vercel.
    • A bug with the Billing system was resolved that caused some Teams to not receive a notification on their Git repository about adding commit authors to their Vercel Team.
    • Personal Accounts that are deleted are now always reliably pruned from our system after the 4 day recovery period. Previously, a special set of them got stuck.
    • The email that is sent after a Personal Account requested to be deleted now correctly considers the new 4 day recovery period (instead of 48 hours).
    Vercel now supports monorepos for improved flexibility at scale. From the same Git repository, you can set up multiple projects to be built and deployed in parallel.
    Monorepos let your team use multiple programming languages and frameworks, collaborate better, and leverage micro frontend architectures.

    Read more →

    August 2020·Changelog
  • Deployments
    • The Node.js version available to newly created Deployments was bumped from 12.16.2 to 12.18.3. No changes to your code are required – you only need to create a new one.
    • The RedwoodJS framework is now automatically detected when creating new Vercel Projects using the Dashboard or Vercel CLI.
    • When redeploying a Deployment or promoting it to Production, a new pipeline is used, which drastically increases the reliability of the features.
    • Custom uploaded SSL Certificates will now take precedence over SSL Certificates that were generated by the system.
    • If a Runtime fails to install from npm during the Build Step of a Deployment, the error will now be surfaced in the build logs.
    • For new Projects, selecting "Other" as the framework preset in the Project Settings will no longer auto-detect the Next.js framework. Existing Projects are not affected.
    • If a vercel-build script is present in package.json, that will be now be preferred over an existing build script.
  • Dashboard
    • The "Visit" button on the Deployment View now always links to the URL of the Deployment – no matter which other Domains were assigned to it.
    • Every Project listed the Dashboard now has a "Updated" indicator, which reflects when the Project's settings were last changed and when a Deployment was created for it the last time.
    • The Production Deployment card on the Project View now uses a deterministic way of deciding your "Primary Domain", which is the Domain that serves your visitors. This is done by finding a Domain in the Project Settings that neither has a Redirect, nor a Git Branch and that is the shortest (alphabetically sorted). Based on that Domain, your current Production Deployment will be resolved.
    • The "Visit" button on the Project View now uses the same logic as described above to determine which Domain to link to.
    • Below the Production Deployment card on the Project View, the upcoming Deployment that will become your current Production Deployment is now rendered.
    • It's now possible to select RedwoodJS as a framework preset in the Project Settings.
    • Toggling the Logs and Source Protection field in the Project Settings will now effect all Deployments created before July 9th, 2020 at 7:05 AM (UTC) too. Deployments created before this date used to be excluded.
    • Screenshots of Deployments will no longer mistakenly render a login screenshot.
    • Creating a new Project from a public GitLab repository will no longer require the destination Vercel scope to be connected to GitLab. Instead, you can also use GitHub or Bitbucket.
    • Creating a new Project will now render a regular text field for the Environment Variable value. It will only change into a larger text field if a multi-line string is pasted or if the shift key is held while pressing enter.
    • It's now possible to create a new Project from a GitLab repository located within a GitLab subgroup.
    • Adjusted Build and Development Settings while creating a new Project from a Git repository or Template will now be retained when changing the viewport width.
    • It's now possible to create a new Team with special characters in its name (such as umlauts) while creating a new Project from a Git repository or Template. Previously, a duplicate Team with a different name was created.
    • Creating a new Project from a Git repository will no longer indefinitely render loading indicators in place of the framework logos within the Root Directory selection page the second time the same Git repository is used.
    • Creating a new Project from a Git repository will no longer retain any errors for subsequent times the same Git repository is used.
    • Updating the Git Integration configuration in the Project Settings will no longer render an empty confirmation toast.
    • It's no longer possible to leave a Team if you're the last confirmed Team Member. In that case, you will be prompted to delete it instead.
    • The buttons for redeploying or deleting a Deployment will no longer be visible for public Deployments that are accessed by someone that is not the owner.
    • When taking a screenshot of a Deployment, the Dashboard will now set a special user agent that allows customers to filter out the request in analytics.
    • The confirmation message that shows up when requesting the deletion of a Personal Account or Team was adjusted to reflect the new deletion buffer time of 4 days.
  • Domains
    • A more helpful "Name" column will now be rendered for CNAME and A DNS Record suggestions on the Domains page in the Project Settings.
    • Whenever a Domain is configured using a CNAME or A DNS Record, but also contains a conflicting CAA or AAAA record, a helpful message will be rendered on the respective Domain entry in the Project Settings.
  • Integrations
    • Whenever a Deployment created by a Git Integration fails or is canceled, the respective comment on the Pull Request will now reflect the new state.
    • Pull Requests augmented by the Git Integrations will no longer render "In Progress" for both the "Inspect" and the "Preview" URL.
  • Command-Line
    • All commands related to Domains were adjusted to match the Dashboard's behavior.
    • When uploading files for a Deployment, Vercel CLI will now try to re-use existing connections instead of opening many new ones.
    • All the features and behavior related to ZEIT Now 1.0 was removed from Vercel CLI.
    • Whenever vercel dev is invoked for a local directory that is not yet linked to a Vercel Project, the command will automatically offer linking it.
    • A new vercel link command was added for linking your local directory to a Vercel Project.
    • The Development Command invoked by vercel dev will now receive a x-vercel-deployment-url header with every incoming request again.
    • The message that recommends upgrading Vercel CLI will no longer be displayed if the installed version is already the most recent one.
  • Other
    • All documentation pages related to ZEIT Now 1.0 were removed.
    • Tokens will now expire after 10 days of inactivity.
    • All packages owned by Vercel that have names starting with now- or @now were marked as deprecated on npm.
    Vercel was born to help frontend teams succeed at scale. From the ideal developer experience on localhost, to the best performance for your end-user via our Global Edge Network.
    Today we are introducing major end-to-end enhancements, starting with a realtime developer workflow (with Next.js and Vercel CLI) and finishing with serving pages up to 6x faster.

    Read more →