Skip to content

chore(Tactic): rewrite match_scalars and module tactic docstrings… #22691

chore(Tactic): rewrite match_scalars and module tactic docstrings…

chore(Tactic): rewrite match_scalars and module tactic docstrings… #22691

Triggered via push March 30, 2026 12:44
Status Success
Total duration 14m 54s
Artifacts 2

bors.yml

on: push
ci (staging)  /  Upload to cache
1m 18s
ci (staging) / Upload to cache
ci (staging)  /  Post-Build Step
2m 53s
ci (staging) / Post-Build Step
ci (staging)  /  Post-CI job
9s
ci (staging) / Post-CI job
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
ci (staging) / 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 (staging) / 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 (staging) / 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
124 MB
sha256:c76a12a3a2a343c481c6d52785e102f6b1be875fec90300e42e4d4f692fc36c8
import-graph
284 KB
sha256:6ebd0ff701d7bd5b25c55dd6df1acd96fe297855a30be8c84aeee11ac4c1fb8d