Update Vercel Runtime to Fix Serverless Function Deployment Error #292
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@amr-sheriff is attempting to deploy a commit to the ryo-ma's Team Team on Vercel. A member of the Team first needs to authorize it. |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
ryo-ma
approved these changes
Aug 27, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Fix an issue where deploying serverless functions on Vercel with the outdated runtime
[email protected]results in an error. The error occurs due to the runtime being invalid for the functions specified.The error encountered during deployment is:
Changes Made
Updated the runtime from
[email protected]to[email protected]in the Vercel configuration file.Impact
This change resolves the deployment error and ensures that the serverless functions are deployed correctly on Vercel without any runtime-related issues.
Testing
The change was tested by redeploying the functions after the runtime update, and the deployment was successful without errors.