Update CHANGES #1146
ci.yml
on: push
ci
51s
ci-clang
24s
ci-gcc
10s
ci-valgrind
35s
ci-scan-build
43s
ci-bindings
1m 0s
docs
36s
release
58s
Annotations
3 warnings
|
docs
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/
|
|
ci-windows
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/msvc-dev-cmd@v1. 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/
|
|
release
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: softprops/action-gh-release@v2. 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 | |
|---|---|---|---|
|
docs-adoc
|
727 KB |
sha256:92f0c9a4f605b8e14915fb323130fb63a0378b0d90a8f47e1d8df9240ea670c6
|
|
|
docs-html
|
780 KB |
sha256:1ae55d12846b86c4d9a94ad7c12f855027b121ecb39bc133435cab1b77419c98
|
|
|
docs-pdf
|
893 KB |
sha256:e73b4ac06f433d4ac9783070c82c371338814012c18256dc8f3e43d48e7bad1f
|
|
|
docs-scribus
|
737 KB |
sha256:aeaad26ddaf1e7d789bc0df3b59ac20526a6b958033676ea0f0e7e1bf1050e4f
|
|
|
monolithic-barcode-ps
Expired
|
502 KB |
sha256:93d5c9c14954947022fbb04adb40e7f7e6c21f7914464bb2c37b582d1bc2174e
|
|