You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 201dcf1
Browse filesBrowse the repository at this point in the historyBrowse files
Prepare browser releases matched to consumer Playwright pins (#41)
A consumer Playwright bump can leave the runner without an accepted
matching browser image. The watcher checks flowbite-xor main hourly,
resolves the selected ref to an immutable commit, validates the exact
manifest/lock pin, and proposes a matching browser release. Manual and
repository-dispatch triggers support coordinating the release before the
consumer bump merges.
Each runtime minor owns its npm lock and parity fixture. COPY inputs,
fingerprints and validation selection isolate line changes. The watcher
captures an accepted application-image digest once and preserves it on
retries, even as the catalog grows. Inventory must match the authored
Playwright version. Candidates retain RGB rendering and committed
screenshot parity.
Includes #39's publication isolation: consumer code executes only on a
fresh job without repository permissions, persisted checkout credentials
or registry login, using controlled Compose configuration and a minimal
environment. Separate finalization accepts evidence only for the exact
public digest, source, image inputs and fixture.
Depends on #39; merge #39 first. The input-layout change allocates
revision 1.0.2 rather than reusing 1.0.1. The current consumer remains
on 1.58.2. Publication/catalog acceptance and review still gate
availability; automatic merge is not enabled.
Validation: all 261 combined tests pass, including cross-line isolation,
retry idempotence, application-pin stability, evidence binding and
publication isolation. Catalog, compilation, shell/YAML and whitespace
checks pass. Updated CI is running. Both existing Codex findings have
fixes and resolved threads; #40 had no findings.
"Use RGB subpixel rendering to match the consuming project's Noble Chromium screenshot baselines; verify fontconfig and committed screenshot parity."
48
+
"Retain RGB screenshot parity and isolate browser locks and fixtures by runtime line; prepare matched releases when the consumer Playwright pin changes."
49
49
],
50
-
"migration": "Compatible rendering fix. Select the accepted 1.0.1 digest after publication; existing 1.0.0 digest pins remain unchanged."
50
+
"migration": "Select the accepted 1.0.2 digest after publication for isolated browser inputs and RGB rendering. Existing exact release pins remain unchanged.",
0 commit comments