Repository navigation
Release 0.19.1 - #255
Merged
Merged
Release 0.19.1#255
Conversation
0.19.0's tag was refused by its own release checks before anything was built or published (the browser check's runtime pin had fallen more than 14 days behind Chrome's Stable channel). A tag never moves, so the release ships as 0.19.1: the version, the CHANGELOG section (renamed, with the reason under Release infrastructure), the roadmap, and PLAN's release records (0.19.0 never published; 0.19.1 preparation). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…rator The 0.19.0 release stopped at its browser-pin check: 156.0.8078.47 was published 21.060 days after the pinned 154.0.8037.92. The pin was hand-built; scripts/pin-browser-runtime.mjs now writes it. - The version, revision and ChromiumDash dates come from the sources the pin check reads, now shared in scripts/lib/browserRuntimeSources.mjs (the check's ChromiumDash query lists its parameters in the order the pin records them; same parameters, same answer). - Each archive is downloaded and measured: length and SHA-256, the end record's entry count, the central directory's uncompressed total, the entries with an execute bit, then read and extracted by zipExtract.ts's own readZipEntries and extractZipEntries, and the extracted executable hashed. The pin passes parseRuntimeManifest before prettier writes it. - Run for 154.0.8037.92 it reproduces the committed pin byte for byte on all four platforms; the new pin is 156.0.8078.47 (r1706539), published 2026-10-20T19:56:54.652Z. - On Win11 the store downloaded, verified, extracted and launched it: the restart capture ended restartObserved and the live suite and R51 passed 8 of 8 (docs/certification/m81.md). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…hrome for Testing 156 # Conflicts: # CHANGELOG.md
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
…nt run PR #255's first runs were red only in the capacity hand-offs: GitHub's incident 'Delays for Pull Requests and Webhook deliveries' created no capacity run within ten minutes of the push. A rerun on the same commit is refused (AGENTS.md rule 2), so this record is the new commit. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
![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: 23f15583ca
ℹ️ 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".
…eason PR #255's second run went red on hosted Windows only: the store read came back 'unavailable' (the same shard passes here) and an integration case ran past its 20 s timeout at twice its usual time, in the hour after GitHub's Actions incident. The test said only the status; it now names the reason, so a repeat shows its cause. Recorded in cifinal0190 §14. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ment the pin commands Chrome for Testing's and ChromiumDash's JSON reached the pin generator and the pin check before any schema read it. Both now parse each answer with a zod schema shared in scripts/lib/browserRuntimeSources.mjs before using a field of it; a wrong shape fails with the URL and the field. The README's Browser check section gives both commands, the optional version, the download size and what to update after a new pin. Proved against the live sources: the generator reproduces browserRuntime.json byte for byte; with the revision pattern broken both scripts exit 1 naming channels.Stable.revision; restored, both exit 0 (docs/certification/cifinal0190.md section 15). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Merged
RandyNorthrup
added a commit
that referenced
this pull request
Oct 22, 2026
Both went red on slow hosted Windows runners in code nothing here changed: runnerHelperNative's native job case passed 60 s (about 7 s on this PC), and the schedule background entry case passed the integration runs' 20 s budget twice (PR #255, PR #257; 7 to 11 s warm). Owner's rule (2026-10-16): no limit of ours that is not about a model. The native case, its status poll and its PowerShell probe now wait however long the machine takes; each schedule-entry test is .timeout(0) (mocha copies a suite's timeout into a test as it is added, so it is set on each test). The other suites keep the repository's budget. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release 0.19.1, the first published 0.19 release.
v0.19.0was tagged on PR #237's merge (e48e8c6bce) but never published: release run 39569020330 stopped at its own tag checks, before building anything, because the browser check's pinned Chrome for Testing runtime (154.0.8037.92) had fallen more than 14 days behind Chrome Stable (156.0.8078.47). A tag never moves (docs/RELEASING.md), so the release ships as 0.19.1.What changes against
main:scripts/pin-browser-runtime.mjs. The generator reproduces the old 154 pin byte for byte on all four platforms before it is trusted; on Windows the real runtime store downloaded, verified, extracted and launched 156 (browser-check-restart.mjsand the live browser-check suites).package.json/package-lock.jsonat 0.19.1; CHANGELOG's section renamed[0.19.1], with the reason under Release infrastructure and the pin under Changed; PLAN §10 records 0.19.0 as never published and prepares 0.19.1; the roadmap regenerated.Local gates: build (bundle budgets, split, legal records) 0, the 18 pre-push gates 0,
check-browser-runtime-pin.mjs0.🤖 Generated with Claude Code