Skip to content

v1.57.8.0 feat: browse js/eval --out render-to-file (canonical Chromium for offline rendering) #347

v1.57.8.0 feat: browse js/eval --out render-to-file (canonical Chromium for offline rendering)

v1.57.8.0 feat: browse js/eval --out render-to-file (canonical Chromium for offline rendering) #347

Triggered via pull request June 9, 2026 18:19
Status Success
Total duration 51s
Artifacts

version-gate.yml

on: pull_request
Check VERSION is not stale vs queue
27s
Check VERSION is not stale vs queue
Fit to window
Zoom out
Zoom in

Annotations

1 warning and 1 notice
Check VERSION is not stale vs queue
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Check VERSION is not stale vs queue
PR #1929 claims v1.57.8.0, below util's suggestion v1.59.1.0. Slot is unclaimed; gate passes. If this PR lands ahead of queued PRs at higher slots, version ordering on main remains monotonic.