Skip to content

update from Kahu's feedback - thanks #55

update from Kahu's feedback - thanks

update from Kahu's feedback - thanks #55

Triggered via push March 11, 2026 23:20
Status Failure
Total duration 51s
Artifacts

checks.yml

on: push
Determine what files to check
5s
Determine what files to check
Check Spelling
21s
Check Spelling
Check Prose
7s
Check Prose
Check Markdown
15s
Check Markdown
Check page meta
9s
Check page meta
Test build
41s
Test build
Fit to window
Zoom out
Zoom in

Annotations

1 error and 27 warnings
Check Prose
Process completed with exit code 1.
Determine what files to check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, tj-actions/changed-files@v40. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Check Prose
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Check page meta
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
walk_toc: docs/user-guides/launch-and-manage-instances/information-about-flavors.md#L11
Header 'Compute Flavors' is a useless only-child. Give it siblings or remove it.
minimum_tags: docs/user-guides/launch-and-manage-instances/information-about-flavors.md#L1
'tags' property in meta is missing or malformed.
meta_unexpected_key: docs/user-guides/launch-and-manage-instances/information-about-flavors.md#L8
Unexpected parameter in front-matter 'vote_sum'
meta_unexpected_key: docs/user-guides/launch-and-manage-instances/information-about-flavors.md#L7
Unexpected parameter in front-matter 'vote_count'
meta_unexpected_key: docs/user-guides/launch-and-manage-instances/information-about-flavors.md#L5
Unexpected parameter in front-matter 'position'
meta_unexpected_key: docs/user-guides/launch-and-manage-instances/information-about-flavors.md#L3
Unexpected parameter in front-matter 'label_names'
meta_unexpected_key: docs/user-guides/launch-and-manage-instances/information-about-flavors.md#L2
Unexpected parameter in front-matter 'hidden'
meta.siblings: docs/user-guides/launch-and-manage-instances/information-about-flavors.md#L1
Parent category 'user-guides' has too many children (9). Try to keep number of items in a category under '8', maybe add some new categories?
Check Markdown
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Check Spelling
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
root: plugin.py#L353
First revision timestamp is older than last revision timestamp for page user-guides/upload-and-manage-images/information-about-images.md. This can be due to a quirk in `git` follow behaviour. You can try to set `enable_git_follow: false` in the plugin configuration.
mkdocs.plugins: docs/user-guides/upload-and-manage-images/information-about-images.md#L196
[git-revision-date-localized-plugin] '/home/runner/work/research-developer-cloud/research-developer-cloud/docs/user-guides/upload-and-manage-images/information-about-images.md' has no git logs, using current timestamp