Allow pattern-matching in variable definitions #9182
Triggered via pull request
November 22, 2024 19:21
Status
Success
Total duration
1h 10m 9s
Artifacts
–
ci.yml
on: pull_request
pre-commit
11s
ormolu
38s
build-and-test-linux
1h 10m
build-and-test-macos
0s
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
|