Skip to content

Fix Windows CI: update swift-docc-plugin to 1.4.6 #267

Fix Windows CI: update swift-docc-plugin to 1.4.6

Fix Windows CI: update swift-docc-plugin to 1.4.6 #267

Triggered via pull request April 2, 2026 19:19
Status Failure
Total duration 36m 17s
Artifacts

SyntaxKit.yml

on: pull_request
Configure Build Matrix
4s
Configure Build Matrix
Matrix: Build for Android
Matrix: Build on macOS (Full)
Matrix: Build on macOS
Matrix: Build on Ubuntu
Matrix: Build on Windows
Linting
Linting
Documentation Validation
Documentation Validation
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 27 warnings
Build for Android (6.2, 34)
The process '/usr/bin/sh' failed with exit code 1
Build for Android (6.2, 33)
The process '/usr/bin/sh' failed with exit code 1
Build for Android (6.3, 34)
The process '/usr/bin/sh' failed with exit code 1
Build for Android (6.3, 33)
The process '/usr/bin/sh' failed with exit code 1
Build on Ubuntu (noble, 6.3, wasm-embedded)
Found .xctest bundles in Wasm build (unexpected - Wasm builds should produce .wasm files)
Build on Ubuntu (noble, 6.0, wasm)
Found .xctest bundles in Wasm build (unexpected - Wasm builds should produce .wasm files)
Build on Ubuntu (jammy, 6.3, wasm-embedded)
Found .xctest bundles in Wasm build (unexpected - Wasm builds should produce .wasm files)
Build on Ubuntu (jammy, 6.1, wasm-embedded)
Found .xctest bundles in Wasm build (unexpected - Wasm builds should produce .wasm files)
Build on Ubuntu (noble, 6.1, wasm-embedded)
Found .xctest bundles in Wasm build (unexpected - Wasm builds should produce .wasm files)
Build on Ubuntu (jammy, 6.2, wasm)
Found .xctest bundles in Wasm build (unexpected - Wasm builds should produce .wasm files)
Build on Ubuntu (noble, 6.1, wasm)
Found .xctest bundles in Wasm build (unexpected - Wasm builds should produce .wasm files)
Build for Android (6.2, 34)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. 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/
Build for Android (6.2, 33)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. 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/
Build for Android (6.3, 34)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. 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/
Build for Android (6.3, 33)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. 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/
Build on Ubuntu (jammy, 6.3, wasm)
Found .xctest bundles in Wasm build (unexpected - Wasm builds should produce .wasm files)
Build on Ubuntu (noble, 6.2, wasm)
Found .xctest bundles in Wasm build (unexpected - Wasm builds should produce .wasm files)
Build on Ubuntu (jammy, 6.2, wasm-embedded)
Found .xctest bundles in Wasm build (unexpected - Wasm builds should produce .wasm files)
Build on Ubuntu (noble, 6.0, wasm-embedded)
Found .xctest bundles in Wasm build (unexpected - Wasm builds should produce .wasm files)
Build on Ubuntu (jammy, 6.0, wasm)
Found .xctest bundles in Wasm build (unexpected - Wasm builds should produce .wasm files)
Build on Ubuntu (noble, 6.2, wasm-embedded)
Found .xctest bundles in Wasm build (unexpected - Wasm builds should produce .wasm files)
Build on Ubuntu (noble, 6.3, wasm)
Found .xctest bundles in Wasm build (unexpected - Wasm builds should produce .wasm files)
Build on Ubuntu (noble, 6.3, wasm)
Failed to restore: The specified blob does not exist. RequestId:f0eb8077-901e-0000-73d7-c2cbe1000000 Time:2026-04-02T19:33:02.4179750Z
Build on Ubuntu (jammy, 6.1, wasm)
Found .xctest bundles in Wasm build (unexpected - Wasm builds should produce .wasm files)
Build on Ubuntu (jammy, 6.0, wasm-embedded)
Found .xctest bundles in Wasm build (unexpected - Wasm builds should produce .wasm files)
Build on macOS (Full) (ios, macos-26, /Applications/Xcode_26.4.app, iPhone 17 Pro, 26.4, true)
DerivedData cache has been restored with same key: xcode-deriveddata-macOS-26.4-31ae34a0e53690a9961677e5977a663f15f94818f2762f060af770ee9eab5480-b330cc039ae8f452e1aa47a899467c74462be6fbef63fa6111e155f60816c169-false-e1656fb7c2fc97cb5603baaefe8b9d2987425d28
Build on macOS (Full) (tvos, macos-26, /Applications/Xcode_26.4.app, Apple TV, 26.4, true)
DerivedData cache has been restored with same key: xcode-deriveddata-macOS-26.4-31ae34a0e53690a9961677e5977a663f15f94818f2762f060af770ee9eab5480-b330cc039ae8f452e1aa47a899467c74462be6fbef63fa6111e155f60816c169-false-e1656fb7c2fc97cb5603baaefe8b9d2987425d28
Build on macOS (Full) (visionos, macos-26, /Applications/Xcode_26.4.app, Apple Vision Pro, 26.4, ...
DerivedData cache has been restored with same key: xcode-deriveddata-macOS-26.4-31ae34a0e53690a9961677e5977a663f15f94818f2762f060af770ee9eab5480-b330cc039ae8f452e1aa47a899467c74462be6fbef63fa6111e155f60816c169-false-e1656fb7c2fc97cb5603baaefe8b9d2987425d28