Skip to content

Fix pod install issue when git's core.fsmonitor feature is enabled #1085

Fix pod install issue when git's core.fsmonitor feature is enabled

Fix pod install issue when git's core.fsmonitor feature is enabled #1085

Triggered via pull request November 22, 2023 00:46
Status Success
Total duration 20m 34s
Artifacts

Specs.yml

on: pull_request
Matrix: specs
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
SPECS / ubuntu-20.04 / Ruby 2.6
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
SPECS / ubuntu-20.04 / Ruby 2.7
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
SPECS / ubuntu-20.04 / Ruby 3
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
SPECS / macos-12 / Ruby system
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
EXAMPLES / macos-12 / Ruby system
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/