mirror of
https://github.com/heygen-com/hyperframes.git
synced 2026-09-01 19:42:03 +00:00
ukimsanov
e94a458fed
Both P1s from Miguel's review on #2976. **The weekly changelog command has a fourth output, and it is public.** `changelog-process.mdx` listed three internal drafts. `outputWeeklyDraft` also calls `prependDocsUpdate` on `--write` (`scripts/changelog-weekly.ts:236`), which writes straight into `docs/weekly-updates.mdx`. A contributor following the page would review three files and push a fourth unread. Now called out as a warning, with the re-run behaviour, since that is what makes editing the entry afterwards safe. The same paragraph also said Weekly updates is "unlisted in the sidebar". That was true when written and I made it false myself, putting the page back under Explore in #2978 after Rames found it orphaned. Corrected rather than reverted — the page belongs in the sidebar. **Bare `hyperframes lint` cannot validate a registry item.** Both `contributing.mdx` and `contributing/catalog.mdx` told contributors to run it. The CLI resolves a project by looking for `index.html` (`packages/cli/src/utils/project.ts`), and registry items ship as `<name>.html` or `demo.html`, so it fails with "No composition found". This is not theoretical: `scripts/lint-registry-items.mjs` exists precisely for this shape and its header records two `gsap_non_transform_motion` errors that reached main unlinted because of it. Both pages now document `bun run lint:registry-items`, and the Catalog page shows the install-into-a-scratch-project route for the full `check` gate rather than claiming a bare `check` covers a registry item. Verified by running the documented command, not just by reading the script.