Skip to content

fix: regenerate source-files manifest#524

Merged
Ehesp merged 1 commit into
mainfrom
fix/regenerate-source-files
Jul 8, 2026
Merged

fix: regenerate source-files manifest#524
Ehesp merged 1 commit into
mainfrom
fix/regenerate-source-files

Conversation

@claude

@claude claude Bot commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

Requested by Elliot Hesp · Slack thread

Fixes #

Summary

Before — the Source Code browser on the homepage fails to load certain mdx files. For example, clicking docs/assets.mdx returns // Failed to load docs/assets.mdx, because the generated manifest (app/src/components/homepage/source-files.json) had gone stale: it still listed files that were since renamed/removed (e.g. docs/assets.mdx, several docs/assets/*.png) and was missing files that have since been added.

After — the manifest is regenerated so it reflects the current repository tree. Stale entries like docs/assets.mdx are removed and current files are present, so the Source Code browser resolves and loads them correctly.

How — this change is purely the output of bun run generate:source-files (which runs app/scripts/generate-source-files.ts). No source logic changed; only the generated manifest was updated (148 insertions, 39 deletions).

Scope

  • app/ (hosted site, MCP, Ask AI)
  • packages/cli/
  • packages/mdx-bundler/
  • docs/ (product documentation)
  • Repo / CI / other

Type of change

  • Bug fix
  • New feature
  • Documentation
  • Refactor / chore

Test plan

  • bun run check passes locally
  • Tested locally (bun dev, CLI command, or other relevant command)
  • Updated docs/ (if user-facing)
  • Verified on a docs.page URL or local preview (if rendering/routing changed)

Regenerated via bun run generate:source-files; confirmed docs/assets.mdx no longer appears in the manifest and current docs mdx entries (verified a sample) resolve to real files on disk.

Notes for reviewers

The manifest goes stale whenever docs/source files are added or removed. This PR just refreshes it; consider automating regeneration in CI as a follow-up so it doesn't drift again.


Generated by Claude Code

@CLAassistant

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@railway-app
railway-app Bot temporarily deployed to docs.page / docs.page-pr-524 July 8, 2026 19:56 Destroyed
@Ehesp
Ehesp marked this pull request as ready for review July 8, 2026 19:57
@Ehesp
Ehesp merged commit ff7e740 into main Jul 8, 2026
3 checks passed
@Ehesp
Ehesp deleted the fix/regenerate-source-files branch July 8, 2026 19:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants