Skip to content

Move vespa search result order tests into a separate file #362

Move vespa search result order tests into a separate file

Move vespa search result order tests into a separate file #362

Triggered via pull request September 17, 2024 12:23
Status Success
Total duration 7m 14s
Artifacts

ci-cd.yml

on: pull_request
check-auto-tagging-will-work  /  check-auto-tagging-will-work
9s
check-auto-tagging-will-work / check-auto-tagging-will-work
manual-semver  /  semver
manual-semver / semver
tag  /  determine-next
0s
tag / determine-next
tag  /  ...  /  semver
tag / semver / semver
release  /  auto-release
release / auto-release
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 1 warning
check-auto-tagging-will-work / check-auto-tagging-will-work
The template is not valid. climatepolicyradar/get-next-tag-from-pr-body/v4/action.yml (Line: 76, Col: 18): Error reading JToken from JsonReader. Path '', line 0, position 0.,climatepolicyradar/get-next-tag-from-pr-body/v4/action.yml (Line: 77, Col: 20): Error reading JToken from JsonReader. Path '', line 0, position 0.
code-quality / python
The template is not valid. climatepolicyradar/get-next-tag-from-pr-body/v4/action.yml (Line: 76, Col: 18): Error reading JToken from JsonReader. Path '', line 0, position 0.,climatepolicyradar/get-next-tag-from-pr-body/v4/action.yml (Line: 77, Col: 20): Error reading JToken from JsonReader. Path '', line 0, position 0.
code-quality / python
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/