Repository navigation
release: prepare v0.13.0 - #53
Merged
Merged
Conversation
Entry points toward 1.0 (/auto, /all, the default deprecated), dist/ untracked, MIT LICENSE, the accessibility and lifecycle audit, sizes decided after layout, and CI dealt by measured time. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FauCMhuVzQvUy2RZAXchUa
`npm run verify` for 0.13.0 saw demo QA pass only on its retry. With one core kept busy, four checks of the functional block failed in turn, each a fixed sleep shorter than the effect it waits for: the class-only Reveal hook (40 ms), the Loader's eased progress (180 ms), Overflow Text rolling on its own timer (1.65 s), Text Transition next() (1.05 s) and the dynamic noise frame counter (180 ms). Each now polls its condition with a bound (1.5-4 s); the assertions are the same. 5/5 with a core busy, 4/4 idle. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FauCMhuVzQvUy2RZAXchUa
npm run release:prepare -- minor on top of the audit / CI-speed branch (agent/claude/perf-a11y-ci): every version source at 0.13.0, the [Unreleased] notes moved into [0.13.0] (20 English + 20 Korean bullets: entry points /auto and /all with the default's meaning deprecated, MIT LICENSE, dist/ untracked, package lint, the accessibility and lifecycle audit, sizes decided after layout, CI dealt by measured time), release notes .github/release-notes/v0.13.0.md, regenerated contract docs, integrations, site and docs/module-cost.md (core 16.1 KB gzip). docs/consumer-bundle-size.md re-measured. The Tests bullet also names the demo QA polling fix. Checks: npm run verify (lint, build, Node 64/64, demo QA, Chromium lane 48/48 with no flake, pack, 5 lockfile audits 0 vulnerabilities), check-release, test:node 64/64 again after the notes edit. Publishing stays a separate, explicitly approved step: npm run release:ship -- v0.13.0 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FauCMhuVzQvUy2RZAXchUa
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
…ry PR dist/ stopped being tracked, but three jobs still read the old committed copy: the weekly supply-chain audit (package size and tarball checks), the weekly live-site parity check (hashes the live runtime against dist/), and the tag-only MCP release (test:contract imports dist/kineto.js). The first two failed on their first Monday run after #52; the MCP release would have failed at its next tag. Each job now runs `npm run build` first. The MCP release also checks that the build leaves tracked files unchanged, so the tarball it packs is exactly the tagged source. tests/workflow-build-order.mjs reads every job of every workflow in order and fails when a command that reads dist/ comes before `npm run build`. Readers are found by following npm scripts and the Node files they run (and the local modules those import), not from a hand-kept list; on the unfixed tree it reports exactly these three jobs. Fixtures pin wrapper arguments, `for` lists, imports, other packages, comments and job boundaries. Docs: the changelog and release notes no longer claim every workflow already built; AI-HANDOFF, RELEASING, supply-chain and QA_REPORT record the jobs, the gate, and the backup sync that went back to an August build on 2026-09-29. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FauCMhuVzQvUy2RZAXchUa
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
2 participants
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.
Entry points (/auto, /all), accessibility and lifecycle audit, CI by measured time. See CHANGELOG [0.13.0].