Skip to content
Publish NPM package

fix: Check if the notification has a mapped component (#560) #269

Sign in to view logs

fix: Check if the notification has a mapped component (#560)

fix: Check if the notification has a mapped component (#560) #269

Triggered via push September 5, 2024 16:10
@kevinszuchetkevinszuchet
pushed fad8d7e
master
Status Success
Total duration 9m 45s
Artifacts –

master.yml

on: push
build
3m 58s
build
deploy
3m 25s
deploy
release
1m 53s
release
Fit to window
Zoom out
Zoom in

Annotations

1 error and 3 warnings
build
Process completed with exit code 1.
build
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
deploy
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
release
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/