fix(ci): skip security scan on forks to avoid SARIF upload permission… #1
test-extra.yml
on: push
detect-changes
11s
tests-llama-cpp-smoke
1m 14s
tests-transformers
tests-rerankers
tests-diffusers
tests-coqui
tests-moonshine
tests-pocket-tts
tests-qwen-tts
tests-qwen-asr
tests-nemo
tests-voxcpm
tests-liquid-audio
tests-llama-cpp-quantization
tests-llama-cpp-grpc
tests-llama-cpp-grpc-transcription
tests-sherpa-onnx-realtime
tests-sherpa-onnx-grpc-transcription
tests-whisper-grpc-transcription
tests-parakeet-cpp-grpc-transcription
tests-sherpa-onnx-grpc-tts
tests-ik-llama-cpp-grpc
tests-turboquant-grpc
tests-acestep-cpp
tests-qwen3-tts-cpp
tests-rfdetr-cpp
tests-locate-anything-cpp
tests-vibevoice-cpp
tests-vibevoice-cpp-grpc-tts
tests-vibevoice-cpp-grpc-transcription
tests-localvqe-grpc-transform
tests-voxtral
tests-kokoros
tests-insightface-grpc
tests-speaker-recognition-grpc
Annotations
1 warning
|
tests-llama-cpp-smoke
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@v5. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|