Skip to content

Part #686, Update cFS Bundle for v7.0.1 #483

Part #686, Update cFS Bundle for v7.0.1

Part #686, Update cFS Bundle for v7.0.1 #483

Triggered via pull request April 30, 2026 21:50
@jphickeyjphickey
synchronize #486
dev
Status Failure
Total duration 2m 42s
Artifacts 1

build-documentation.yml

on: pull_request
Build and deploy cFS documents  /  checks-for-duplicates
4s
Build and deploy cFS documents / checks-for-duplicates
Matrix: Build and deploy cFS documents / Build Documentation
Fit to window
Zoom out
Zoom in

Annotations

1 error and 2 warnings
Build and deploy cFS documents / Build Documentation (cf-usersguide)
Process completed with exit code 1.
Build and deploy cFS documents / checks-for-duplicates
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: fkirc/skip-duplicate-actions@master. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
Build and deploy cFS documents / Build Documentation (cf-usersguide)
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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Artifacts

Produced during runtime
Name Size Digest
cf-usersguide_doc_build_logs Expired
14.7 KB
sha256:a04b1874e01fe6cda292c14ca83dc5df236b1f168e2ae7c987bb12f4dc4c6de0