fix(site): remove static release labels#4
Conversation
Why: - mycel.run was still serving hard-coded release labels, and the site source still had manually maintained version metadata and a stale social image. - The site should not require manual release/version text updates when package badges can reflect live package state. What changed: - Remove the static hero release badge, JSON-LD softwareVersion, alpha notice, and social image metadata from index.html. - Delete the stale og-image.png that contained old release labels. - Add a site metadata guard and GitHub Actions check to prevent reintroducing hard-coded release labels. Testing: - node scripts/check-site-release-metadata.js - git diff --cached --check - rg check against site files for stale version/alpha/social-image markers Risk: - narrow - social previews no longer use a large static image until a generated versionless image is added.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 619bd4d573
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| const html = fs.readFileSync("index.html", "utf8"); | ||
| const jsonLd = html.match( | ||
| /<script type="application\/ld\+json">\n([\s\S]*?)\n<\/script>/, |
There was a problem hiding this comment.
The regex used to extract the JSON-LD block hard-codes \n delimiters, so it fails when index.html is saved with CRLF (common on Windows checkouts), causing CI to throw index.html is missing JSON-LD metadata even though the script tag exists. This makes the new site guard flaky across contributor environments and can block unrelated PRs; matching \r?\n (or parsing the script block without newline assumptions) avoids that false failure.
Useful? React with 👍 / 👎.
1 participant
Summary
Issue: N/A
Test plan
Risk