Skip to content

Fix bug in ComputeTypeInfo for let #9015

Fix bug in ComputeTypeInfo for let

Fix bug in ComputeTypeInfo for let #9015

Triggered via pull request November 11, 2024 16:08
Status Success
Total duration 1h 8m 53s
Artifacts

ci.yml

on: pull_request
pre-commit
15s
pre-commit
ormolu
31s
ormolu
build-and-test-linux
1h 8m
build-and-test-linux
build-and-test-macos
0s
build-and-test-macos
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
pre-commit
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
ormolu
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build-and-test-linux
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache@v3, jaxxstorm/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build-and-test-linux
x..y inside match is deprecated, you must always match on the step: x..y//var or x..y//_ if you want to ignore it