Skip to content

perf: reduce to single priming round now that activity cache handles … #242

perf: reduce to single priming round now that activity cache handles …

perf: reduce to single priming round now that activity cache handles … #242

Triggered via push April 4, 2026 03:12
Status Failure
Total duration 13m 21s
Artifacts

deploy.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 1 warning
build-and-deploy
HttpError: API rate limit exceeded for installation. If you reach out to GitHub Support for help, please include the request ID 0400:3CF657:25CE818:9459CCC:69D084A7 and timestamp 2026-04-04 03:25:27 UTC. For more on scraping GitHub and how it may affect your rights, please review our Terms of Service (https://docs.github.com/en/site-policy/github-terms/github-terms-of-service)
build-and-deploy
Get Pages site failed. Please verify that the repository has Pages enabled and configured to build using GitHub Actions, or consider exploring the `enablement` parameter for this action.
build-and-deploy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/configure-pages@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/