Skip to content

feat(changelog): play the approved release film - #153

Closed
maximebrmd wants to merge 5 commits into
codex/pr149-1-pipfrom
codex/pr149-2-playback
Closed

maximebrmd wants to merge 5 commits into
codex/pr149-1-pipfrom
codex/pr149-2-playback

Conversation

@maximebrmd

@maximebrmd maximebrmd commented Nov 2, 2026 •

Copy link
Copy Markdown
Collaborator

Why

The maintainer needs to review #149 one change at a time. This adds shared website and native release-media playback before introducing production tools.

What changed

  • Add compact MP4/PNG players, HTTP byte ranges and current-release bundle staging.
  • Keep the approved 0.8.0 film with localized captions and a translated English-language label.
  • Preserve the existing 0.7.0 recording and native artwork while their archive replacements are pending.

Scope

Blast Radius

This touches changelog playback, the native resource handler and UI cache inputs. Missing catalog entries retain their existing presentation.

Verification

  • make validate TEST_WORKERS=4 passed after integrating current main, including native, UI and website checks.
  • Three staging tests passed. Archive staging order and generated resource registration were checked.
  • Browser runs passed 21 What's New cases and 18 website cases on the integrated branch, including the retained 0.7.0 player.

Review after #152. This PR targets its parent branch to keep the diff focused. Retarget to main after the parent merges; hosted CI then runs against the merged parent.

Ordered review guide, validation evidence and stack merge instructions.

@maximebrmd
maximebrmd requested a review from Alexays as a code owner November 2, 2026 20:50
Ignore Range headers that are not a single byte range, compare If-Range
strongly, stream partial responses from the site worker instead of
buffering the film, present a previewed release under the installed
version so the sheet shows it, and run the staging tests in CI.
Drop the media Worker: every film request was a billed invocation.
Cloudflare answers static assets whole, and advertising byte ranges is
enough for Chromium to seek the fully buffered compact film; WebKit
plays and seeks it either way.
@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Nov 2, 2026 •

Copy link
Copy Markdown

🚀 Deploying Preview to Cloudflare 🚀

Preview Deployments by commit

Status Deployment URL Commit Updated (UTC) See this deployment's details
  • Build: Failed ❌

View logs ↗
beb6d49 2026-11-02T22:42:13.159Z View logs ↗
  • Build: Failed ❌

View logs ↗
05128fd 2026-11-02T21:56:25.517Z View logs ↗

@maximebrmd

Copy link
Copy Markdown
Collaborator Author

Replaced by #178, which ports this onto current main with media per highlight and restores the film's 1080p60 master. The branch is kept.

@maximebrmd maximebrmd closed this Nov 6, 2026
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.

2 participants