Skip to content

Fix new remote address being handled as local file by loadUserConfig #7848

Fix new remote address being handled as local file by loadUserConfig

Fix new remote address being handled as local file by loadUserConfig #7848

Triggered via pull request July 14, 2026 22:05
Status Success
Total duration 1m 6s
Artifacts 2

__config-export.yml

on: pull_request
Matrix: Config export
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
Config export (ubuntu-latest, linked)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: fwilhe2/setup-kotlin@9c245a6425255f5e98ba1ce6c15d31fce7eca9da. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Config export (ubuntu-latest, nightly-latest)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: fwilhe2/setup-kotlin@9c245a6425255f5e98ba1ce6c15d31fce7eca9da. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
config-export-ubuntu-latest-linked.sarif.json Expired
83 KB
sha256:6624f2d15e26c0abebf2bd2a3f14836b9de4fe23939a558f17cd4b88458e1237
config-export-ubuntu-latest-nightly-latest.sarif.json Expired
83.1 KB
sha256:490b1d6bc054e81d9387b44362afdea90e11c7586cd34e9c8bc48cd69a068c24