Skip to content

feat: support standard YAML frontmatter via pre-AST replacement #993

feat: support standard YAML frontmatter via pre-AST replacement

feat: support standard YAML frontmatter via pre-AST replacement #993

Triggered via pull request March 24, 2026 13:29
Status Success
Total duration 1m 42s
Artifacts 9

generate.yml

on: pull_request
Matrix: generate
Fit to window
Zoom out
Zoom in

Annotations

10 warnings
prepare
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
generate (man-page, ./node/doc/api/cli.md)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
generate (addon-verify, ./node/doc/api/addons.md)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
generate (api-links, ./node/lib/*.js, object-assertion)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
generate (llms-txt, ./node/doc/api/*.md, file-size)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
generate (legacy-json, ./node/doc/api/*.md, object-assertion)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
generate (orama-db, ./node/doc/api/*.md, file-size)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
generate (json-simple, ./node/doc/api/*.md)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
generate (legacy-html, ./node/doc/api/*.md, file-size)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
generate (web, ./node/doc/api/*.md, file-size)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/

Artifacts

Produced during runtime
Name Size Digest
addon-verify
13 KB
sha256:4da451ea5c8be246813ddeef324bd07bfcd6bb2fd6c7490c708a8a9dbdf27d75
api-links
5.67 KB
sha256:6272838c565d94dd32eed938383f0ab19a4ed62739b0530a8c5c23dd8001c28c
json-simple
2.97 MB
sha256:c750f6f4d19de4e620e73565cc07f80c2dcb7e238b80b10b18f4ba06b114f3ee
legacy-html
1.6 MB
sha256:a5f23931e61d31a9bcc5c26588301de940568ecb08c7aa652feb029c038470af
legacy-json
1.11 MB
sha256:228d1fd66227fb930a73aeb503ed3f0bd562ad493faef1b95ff1670bdc2432ff
llms-txt
4.51 KB
sha256:d89ef78fbe4b4cb7dad16199aa1ffb25c7c0a7e5b34671d97f36ac4f0fd4a64a
man-page
25.1 KB
sha256:658baae9e60e174573841b6f6ec573d54e8daec5d0a3a8ee04c279c4f4f90e01
orama-db
1.6 MB
sha256:7b01eebf47d8a42468137f88fbb00898d1f6a9e53aad4801c9d63a9b3f68bdeb
web
3.82 MB
sha256:d0dec054f0cd04bae3803bad349662c0faf478dc536c5d2f7ea7857354598c91