Streamline release verification and consolidate test coverage - #134
Conversation
- Skip docs during release checks - Reuse the verified tarball without rebuilding - Run core tests once under coverage
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. |
|
Codex Review: Didn't find any major issues. Nice work! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
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". |
|
Codex Review: Didn't find any major issues. Can't wait for the next one! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
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". |
|
Codex Review: Didn't find any major issues. Chef's kiss. Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
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". |
|
Codex Review: Didn't find any major issues. You're on a roll. Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
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". |
1 participant
Reduce repeated verification work while keeping the existing coverage thresholds and browser journeys. Release verification skips docs and publishes the exact tarball that passed its package smoke test.
The full test command collects coverage during one unit and integration pass. Live-update benchmarks remain manual. Direct unit tests now cover note-output limits, with key CLI cases retained. Redundant UI source-text assertions are removed.
Merge main while keeping the deleted source-text test removed. Move the existing Fallow baseline counts with the extracted validators, without increasing the total allowance. Control the provider test deadline after child readiness to remove its startup race. Run Product gate once on Node 24.20.0, the latest LTS when pinned, instead of repeating it for Node 22 and 24. Keep the exact version fixed until an explicit update.
Validation:
corepack pnpm run lintat5543f3a8004859f03cf6cb6c9099e1c72b5a525fGIT_CONFIG_GLOBAL=/dev/null corepack pnpm testat5543f3a8004859f03cf6cb6c9099e1c72b5a525fGIT_CONFIG_GLOBAL=/dev/null corepack pnpm run checkate2f912c4e5703ef8387245998e7b5ee39898becc, before replacing the LTS alias with an exact pin (includes docs checks/build and package smoke)Local tests exclude personal Git settings.
Measured cost before the exact-version pin:
These are observed runs, not a controlled benchmark. Test lanes: before, after. Product gate: two versions, latest LTS only. Parallel job removal cuts runner use; these runs do not show a shorter overall CI wait.
The last release's docs stages and second build/package smoke took about 25s combined. Removing them projects its 2m42s prepare/verify step to about 2m17s, before test savings. This is stage subtraction from the prior release, not a newly measured release.