Skip to content

Fix potential NPEs during export branding and fix Extension example #505

Fix potential NPEs during export branding and fix Extension example

Fix potential NPEs during export branding and fix Extension example #505

Triggered via pull request October 9, 2024 17:48
@HannesWellHannesWell
synchronize #210
Status Success
Total duration 5m 4s
Artifacts 2

buildAndTest.yml

on: pull_request_target
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
build
The following actions uses node12 which is deprecated and will be forced to run on node16: nelonoel/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build
The following actions use a deprecated Node.js version and will be forced to run on node20: nelonoel/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Artifacts

Produced during runtime
Name Size
KLighD MVN Repository Expired
14.5 MB
KLighD P2 Repository Expired
6.8 MB