fix(site): fetch renderer changelog instead of reading it off disk - #3542
Merged
Conversation
Vercel builds this app with apps/site as the root directory, so the sibling packages/renderer/CHANGELOG.md is not there at prerender time and /changelog failed the production build. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
1 participant
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.
Vercel builds
apps/sitewith that folder as the project root directory, so the siblingpackages/renderer/CHANGELOG.mdis not present at prerender time and/changelogfailed the production build withENOENT. This happens even with Include source files outside of the Root Directory enabled and the whole repo cloned.getReleasesnow fetches the changelog fromraw.githubusercontent.cominstead of reading it off disk. Release dates still come from the npm registry, as before.Side benefit: the page is served with
revalidate: 86400from the innerfetch, so a background regeneration in a lambda used to be a latentENOENTtoo. Over the network it works in both places.Verified on the preview deployment: build passes, all 97 pages generate, and
/changelogrenders real releases rather than an empty list.馃 Generated with Claude Code