Skip to content

feat: add blog post for releases releases-2026-04-13-3b744f9a #369

feat: add blog post for releases releases-2026-04-13-3b744f9a

feat: add blog post for releases releases-2026-04-13-3b744f9a #369

Triggered via push April 13, 2026 10:47
Status Success
Total duration 5m 38s
Artifacts 3

main-ci.yml

on: push
ci  /  ...  /  πŸ“¦ Prepare configuration
3s
ci / continuous-integration / πŸ“¦ Prepare configuration
Matrix: ci / continuous-integration-actions
ci  /  ...  /  πŸ›‘️ CodeQL Analysis
1m 31s
ci / continuous-integration / πŸ›‘οΈ CodeQL Analysis
ci  /  ...  /  πŸ›‘️ Dependency Review
ci / continuous-integration / πŸ›‘οΈ Dependency Review
Generate Documentation
45s
Generate Documentation
ci  /  ...  /  βš™οΈ Setup
7s
ci / continuous-integration / βš™οΈ Setup
ci  /  ...  /  πŸ—️ Build
1m 25s
ci / continuous-integration / πŸ—οΈ Build
ci  /  ...  /  πŸ‘• Lint
1m 12s
ci / continuous-integration / πŸ‘• Lint
ci  /  ...  /  πŸ§ͺ Test
46s
ci / continuous-integration / πŸ§ͺ Test
share-new-blog-posts  /  announce
22s
share-new-blog-posts / announce
Fit to window
Zoom out
Zoom in

Annotations

17 warnings
ci / continuous-integration-actions (.github/actions/generate-blog-post) / πŸ—οΈ Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd. 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 / continuous-integration-actions (.github/actions/validate-manifest) / πŸ—οΈ Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd. 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 / continuous-integration-actions (.github/actions/generate-brand-content) / πŸ—οΈ Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd. 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 / continuous-integration-actions (.github/actions/generate-blog-post) / πŸ§ͺ Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd. 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 / continuous-integration-actions (.github/actions/generate-brand-content) / πŸ§ͺ Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd. 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 / continuous-integration-actions (.github/actions/validate-manifest) / πŸ§ͺ Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd. 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 / continuous-integration-actions (.github/actions/generate-brand-content) / πŸ›‘οΈ CodeQL Analysis
Failed to save: Unable to reserve cache with key codeql-trap-1-2.25.1-javascript-f281ff2e7ea0d2eec29d1767747dc7d112ec26a9, another job may be creating this cache.
ci / continuous-integration-actions (.github/actions/generate-brand-content) / πŸ›‘οΈ CodeQL Analysis
Failed to save: Unable to reserve cache with key codeql-overlay-base-database-1-9932c4479c18de1c-javascript-2.25.1-f281ff2e7ea0d2eec29d1767747dc7d112ec26a9-24339298467-1, another job may be creating this cache.
ci / continuous-integration / πŸ‘• Lint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd. 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 / continuous-integration / πŸ‘• Lint
No report files found
ci / continuous-integration / πŸ›‘οΈ CodeQL Analysis
Failed to save: Unable to reserve cache with key codeql-trap-1-2.25.1-javascript-f281ff2e7ea0d2eec29d1767747dc7d112ec26a9, another job may be creating this cache.
ci / continuous-integration / πŸ›‘οΈ CodeQL Analysis
Failed to save: Unable to reserve cache with key codeql-overlay-base-database-1-9932c4479c18de1c-javascript-2.25.1-f281ff2e7ea0d2eec29d1767747dc7d112ec26a9-24339298467-1, another job may be creating this cache.
ci / continuous-integration-actions (.github/actions/validate-manifest) / πŸ›‘οΈ CodeQL Analysis
Failed to save: Unable to reserve cache with key codeql-trap-1-2.25.1-javascript-f281ff2e7ea0d2eec29d1767747dc7d112ec26a9, another job may be creating this cache.
ci / continuous-integration-actions (.github/actions/validate-manifest) / πŸ›‘οΈ CodeQL Analysis
Failed to save: Unable to reserve cache with key codeql-overlay-base-database-1-9932c4479c18de1c-javascript-2.25.1-f281ff2e7ea0d2eec29d1767747dc7d112ec26a9-24339298467-1, another job may be creating this cache.
ci / continuous-integration / πŸ—οΈ Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd. 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 / continuous-integration / πŸ§ͺ Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd. 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/
Deploy website
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/configure-pages@983d7736d9b0ae728b81ab479565c72886d7745b, actions/deploy-pages@d6db90164ac5ed86f2b6aed7e0febac5b3c0c03e, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, treosh/lighthouse-ci-action@fcd65974f7c4c2bf0ee9d09b84d2489183c29726. 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
24339298467-369-github-pages-1776077396909-c0b53e98-3f18-4228-bf52-e34b79c51865 Expired
135 MB
sha256:a8a8a945a04f7077d11c5576d65a0c056b83d97771429b06ee92a8f47a80979c
24339298467-369-lighthouse-results-1776077514612-88438f42-db7e-4f51-91e1-c1c7a4ac0ae4
1.02 MB
sha256:1eba2f5bba8fb52783e7a29c892dc2bfaa79bc3b51fb36b0342978ddb0fc511c
setup-build-24339298467-rbtvw7
105 MB
sha256:47474fe413623c9ed80d70e856c59c40abbe9da9982d692b6bbb4fc459373889