Recommend SCM source context for Go serverless deployments#17684
Open
Recommend SCM source context for Go serverless deployments#17684
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
7286948 to
84a059a
Compare
84a059a to
ce6cbe9
Compare
mujacica
approved these changes
May 8, 2026
cleptric
reviewed
May 8, 2026
|
|
||
| For Go, source context is provided through [SCM Source Context](/integrations/source-code-mgmt/source-context/) with code mappings. | ||
|
|
||
| The Go SDK no longer reads local source files at runtime to populate source context. If you want source lines in stack traces, set up SCM Source Context instead of bundling source files with your deployed binary. |
Member
There was a problem hiding this comment.
I think we can remove this paragraph, something for the SDK changelog instead.
This file contains hidden or 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
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.
DESCRIBE YOUR PR
This updates the Go serverless and troubleshooting docs to recommend SCM Source Context as the preferred way to get source lines in stack traces when a supported SCM integration is available.
It also expands the SCM Source Context page to explain why this is often a better default than bundling repository source into deployed binaries, especially for Go serverless deployments.
IS YOUR CHANGE URGENT?
SLA
Thanks in advance for your help!
PRE-MERGE CHECKLIST
LEGAL BOILERPLATE
EXTRA RESOURCES