Skip to content

chore(plugin-previews): refresh baked preview manifest - #5285

Merged
lefarcen merged 1 commit into
mainfrom
chore/plugin-previews
Jul 9, 2026
Merged

chore(plugin-previews): refresh baked preview manifest#5285
lefarcen merged 1 commit into
mainfrom
chore/plugin-previews

Conversation

@open-design-release-bot

Copy link
Copy Markdown
Contributor

Automated by the bake-plugin-previews workflow: preview clips were re-rendered and uploaded to R2; this updates data/plugin-previews/manifest.json to match (the clips live on R2 and are not committed). This is a single rolling PR — each bake force-updates it in place rather than stacking a new PR per run. @lefarcen please review and merge.

@lefarcen lefarcen added size/XL PR changes 700-1500 lines risk/medium Medium risk: regular code changes type/chore CI / build / config / tooling labels Jul 8, 2026
@github-actions
github-actions Bot force-pushed the chore/plugin-previews branch 2 times, most recently from 8ae7aaa to 25e1612 Compare July 8, 2026 18:18
@lefarcen

lefarcen commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

Thanks for keeping the baked preview manifest in sync. Could you add a short PR summary covering Why, What users will see, Surface area, and Validation? Even for the rolling manifest refreshes, that context makes pool review and release audit much easier.

@github-actions
github-actions Bot force-pushed the chore/plugin-previews branch from 25e1612 to eca6501 Compare July 8, 2026 19:07
@github-actions
github-actions Bot force-pushed the chore/plugin-previews branch from eca6501 to 2612f90 Compare July 9, 2026 07:43

@lefarcen lefarcen left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving: rolling plugin-preview manifest refresh. CI green (run 29002397592, re-run to clear the github-actions[bot] approval gate). Verified safe to land despite the automerge base-freshness skip — main's data/plugin-previews/manifest.json is untouched between the render base (49d64f0) and current main HEAD (87a6a1a), so this squash replaces the stale 06-30 manifest with the latest render (incl. the 15 webgl clips) with no risk of overwriting a newer manifest.

@lefarcen
lefarcen added this pull request to the merge queue Jul 9, 2026
Merged via the queue into main with commit fb4d48c Jul 9, 2026
17 checks passed
liny90626 pushed a commit to liny90626/open-design that referenced this pull request Jul 12, 2026
v0.14.1 ships the 15 WebGL example templates (nexu-io#5266 + nexu-io#5312, both merged
before the 07-09 03:35 cut) but its bundled data/plugin-previews/manifest.json
has zero entries for them: the manifest refresh that baked their clips (nexu-io#5285)
merged to main ~6h AFTER the cut, and the release-branch bake never populated
v0.14.1. Without a baked entry the home gallery falls back to rendering each
template as a LIVE example.html iframe — and these are real-time WebGL/GPU
shaders, so a grid of them is exactly the pathological lag the baked-preview
pipeline exists to avoid.

The daemon serves baked previews by plugin id (loadManifest(dir)[id]) with no
runtime fingerprint re-check, and the 15 clips + posters are already immutable
on R2 (all 15 verified 206 video/mp4). So adding the entries to the committed
manifest is sufficient and safe: the packaged v0.14.1 app plays the baked H.264
clips instead of spinning up live WebGL contexts.

Purely additive: +15 previews entries, no existing entry touched.
xxiaoxiong pushed a commit to xxiaoxiong/open-design that referenced this pull request Jul 13, 2026
Co-authored-by: open-design-bot <bot@open-design.ai>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

risk/medium Medium risk: regular code changes size/XL PR changes 700-1500 lines type/chore CI / build / config / tooling

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant