Skip to content

Fix reporting the current locator when submitting new preferences #750

Fix reporting the current locator when submitting new preferences

Fix reporting the current locator when submitting new preferences #750

Triggered via pull request August 27, 2024 14:14
Status Success
Total duration 20m 36s
Artifacts

checks.yml

on: pull_request
Integration (Local)
4m 19s
Integration (Local)
Integration (Swift Package Manager)
2m 59s
Integration (Swift Package Manager)
Integration (Carthage)
20m 25s
Integration (Carthage)
Integration (CocoaPods)
0s
Integration (CocoaPods)
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
Lint
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, pnpm/action-setup@v2, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Integration (Swift Package Manager)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Integration (Local)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@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
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Integration (Carthage)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/