Skip to content

perf(CategoryTheory/Monoidal/Internal/Types): decrease instance priority #288589

perf(CategoryTheory/Monoidal/Internal/Types): decrease instance priority

perf(CategoryTheory/Monoidal/Internal/Types): decrease instance priority #288589

Triggered via pull request April 14, 2026 15:38
@JovanGerbJovanGerb
opened #38046
Status Success
Total duration 12m 40s
Artifacts 2

build_fork.yml

on: pull_request_target
ci (fork)  /  Upload to cache
1m 9s
ci (fork) / Upload to cache
ci (fork)  /  Post-Build Step
2m 36s
ci (fork) / Post-Build Step
ci (fork)  /  Post-CI job
9s
ci (fork) / Post-CI job
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
ci (fork) / Lint style
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/setup-python@a26af69be951a213d495a4c3e4e4022e16d87065. 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/
ci (fork) / Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: leanprover-community/gh-problem-matcher-wrap@20007cb926a46aa324653a387363b52f07709845. 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/
ci (fork) / Post-CI job
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 8BitJonny/gh-get-current-pr@4056877062a1f3b624d5d4c2bedefa9cf51435c9. 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/

Artifacts

Produced during runtime
Name Size Digest
cache-staging
529 KB
sha256:c3f2285ac217449384841e57071100d6d9df79245300628683634e7f2fcf0412
import-graph
285 KB
sha256:f43507385bd4cfe8c847ebe92d8f3076bc7ae37813bb79ce8b19d964312dcec6