Repository navigation
Fix broken showcase submission backend - #1996
Merged
Merged
Conversation
✅ Deploy Preview for codingtrain ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Collaborator
Author
|
New functions seem to bundle properly in the preview build, and I can see the log error expected when submitting a showcase. Think we need to merge to 
|
dipamsen
approved these changes
Nov 13, 2026
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.
@kfahn22 noticed showcase submissions weren't working anymore.
Logs show that there was an error with Octokit because it doesn't ship CJS anymore (it's now ESM only).
This PR updates the Netlify functions to ESM. It also follows the modern Netlify functions API, as the lambda compat mode API has been deprecated and will start failing in various ways in 2027.
REMINDER: the showcase submission flow in the preview build for this PR is expected to fail because the GitHub token doesn't populate on PRs for security reasons