Skip to content

Merge pull request #59 from gchq/release/v0.0.9 #4

Merge pull request #59 from gchq/release/v0.0.9

Merge pull request #59 from gchq/release/v0.0.9 #4

Triggered via push January 5, 2024 18:16
Status Failure
Total duration 1m 0s
Artifacts

publish.yaml

on: push
Matrix: build
create-release
5s
create-release
publish-npm
14s
publish-npm
Fit to window
Zoom out
Zoom in

Annotations

1 error and 4 warnings
create-release
Validation Failed: {"resource":"Release","code":"already_exists","field":"tag_name"}
build (10.x)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (12.x)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
create-release
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/create-release@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
publish-npm
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/