Skip to content

build: update requests requirement from >=2.32.2 to >=2.33.1 (#1431) #500

build: update requests requirement from >=2.32.2 to >=2.33.1 (#1431)

build: update requests requirement from >=2.32.2 to >=2.33.1 (#1431) #500

Triggered via push May 6, 2026 18:00
Status Failure
Total duration 1m 6s
Artifacts –

on-pr-merge.yml

on: push
Tag Repository as 'latest'
26s
Tag Repository as 'latest'
Build RAMSTK Documentation
1m 0s
Build RAMSTK Documentation
Fit to window
Zoom out
Zoom in

Annotations

1 error and 5 warnings
Build RAMSTK Documentation
Process completed with exit code 2.
Tag Repository as 'latest'
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, crazy-max/ghaction-import-gpg@v5. 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/
Tag Repository as 'latest'
Failed to parse version from input latest. Defaulting coerced version to null.
Tag Repository as 'latest'
Using the first one returned by GitHub API: latest
Tag Repository as 'latest'
Multiple draft releases found : latest, latest, latest, latest, latest, latest, latest, latest, latest, latest, latest
Build RAMSTK Documentation
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-python@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/