Release Arena v12.1.1 · dravensoft-dev/arena

the layer's one ngc emit is its type verdict, and check-all runs it whenever the angular domain is selected

the demo bundle's test names a missing emit in the present tense
the Angular emit is a build step the demo bundles from, so the layer is compiled once per input change
the Angular test emit is skipped when its inputs were rewritten with the same bytes
a step that runs a compiler hands an interrupt to it and waits, so no compiler outlives an interrupted build
the Angular package lists its nested manifests in .npmignore in the order the entry points are declared, whatever order ng-packagr found them in
the pages that name the build commands say what --target builds and who runs it
--target runs one step and every step it reads from, release-only ones included

the repository-wide equivalence case of check-packages declares a deadline that holds beside the sweep's other steps
a job layout the workflow readers cannot follow is a problem, and one workflow names the browser, by its own CHROME_PATH or the chrome-path it passes
the page says pixel-parity encodes every capture the same way, for speed, and compares bytes only between such captures
check:pixel-parity takes every capture through one call, a lossless png encoded for speed
check-all declares a cost beside each pool, so its heavy steps start longest first
the pages that describe check-all say it runs side by side and that check:consumer never builds
check-all runs its gates and suites side by side, one block each, with what each took
check:consumer judges an assembled package and refuses an unassembled one, so no gate beside it meets a rewritten dist/

verify-workflow.ts reads which domains verify.yml's gates take, which job runs each suite and which domains each caller selects
ci:summarize runs one suite into a report of its own and joins the reports a run's domains select
the route prints the domains a diff selects, every domain that is no layer and each layer it reaches

an arena-build- upload keeps the files whose names open with a dot, or check:graph refuses it
a heavy step budgets 1.1 GiB of free memory, the measured compiler peak and a margin, so a machine with about three gigabytes free runs two at once
the pages that describe run-build say it runs side by side, records as each step ends and starts the heavy steps longest first
run-build runs its steps side by side, records each as it ends and blocks only what a failure feeds
the compiler build steps declare their pool and cost, and check:graph refuses a build step reading what a step beside it writes
restamp re-reads what one step's writes reach, under the directories they name
the scheduler starts heavy steps longest first by their declared cost, and one slot keeps the listed order
check:arbitrary and check:architecture declare their frameworks reads without the Angular emit
a scheduler runs steps side by side within pools sized from the machine
what a publish or the site builds on a miss covers every build step its gate reads
check:mcp reads the demo and kitchen-sink pages the prompts name, which the generators write
upstreamOf walks needsOf the way transitiveFeeds walks feeds
every arena-build- cache or artifact step in every workflow carries BUILD_HANDOFF_PATHS, path for path

the pages that describe the typecheck library say it spawns tsc once and hands the gate's interrupt to it
a typecheck gate builds its program once, reading the files tsc read from the same run, and its interrupt reaches tsc
the artifact cache holds a reading whose builder is async, with the same entry and keep rule as the sync one
a browser gate loads a page once more when the host's network changed under it, and says so when it changes twice
childOutputAsync captures a child that runs beside others as one block, and an abort ends it

12.1.1 in the plugin, the marketplace entry, the README and the MCP registry manifest

a portable leg assembles the packages, since check:consumer judges one and check:graph reads what assembling writes
the pages say pull requests, develop and main verify through one reusable workflow, and where its build, gates and suites run
pull requests, develop and main verify through one reusable workflow that builds once and runs the gates and each suite in jobs of their own
a publish or the site that misses its cache builds its own target and what it reads from
the hand-off pages name BUILD_HANDOFF_PATHS and the gate that holds every workflow to it

Every commit: v12.1.0...v12.1.1

Navigation Menu