BWIPP CI #1161
ci.yml
on: push
ci
52s
ci-clang
25s
ci-gcc
17s
ci-valgrind
40s
ci-scan-build
39s
ci-bindings
1m 7s
docs
29s
release
55s
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
|
751 KB |
sha256:e1f6b1b4eedb860f7e4db44ee21302dd2e79e6195f08213a417a3f1c80f4abee
|
|
|
docs-html
|
806 KB |
sha256:bb61149b235d701ba55191c5a99aba2235ed5c7234ad8cf444b88623c5dd0b89
|
|
|
docs-pdf
|
910 KB |
sha256:c141edc316e4e23bcfd42990de0d9292aae501ab2d9523c67dcfa728fd23d42f
|
|
|
docs-scribus
|
760 KB |
sha256:2d4dee0e976ca59eacbfc9223b64289787ae9a5de53b590081db82eb3966bbe6
|
|
|
monolithic-barcode-ps
Expired
|
507 KB |
sha256:2acda5018e92471de418d54cd74131861e29b2afcf7b7aff0aa17bef656ebec3
|
|