Skip to content

feat(workflow): redesign PO scope process — v4 major (Gherkin-first, folder-per-feature, @id tracing) #84

feat(workflow): redesign PO scope process — v4 major (Gherkin-first, folder-per-feature, @id tracing)

feat(workflow): redesign PO scope process — v4 major (Gherkin-first, folder-per-feature, @id tracing) #84

Triggered via pull request April 16, 2026 15:38
Status Success
Total duration 44s
Artifacts 3

ci.yml

on: pull_request
Code Quality & Security
10s
Code Quality & Security
Matrix: Tests
Security Summary
3s
Security Summary
Build & Documentation
19s
Build & Documentation
Publish Documentation
0s
Publish Documentation
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
Code Quality & Security
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608. 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/
Tests (3.13)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608. 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/
Build & Documentation
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608. 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
coverage-reports
34 KB
sha256:22945e3804207a311eca90e94321e578e0f2135f9afdb5836265d104bec77eb4
documentation
14.1 KB
sha256:6ecac9f2710a44cdfdf24d3e38fda836cabd93339b84d069ccb2995d81ac8e4f
python-package-distributions
12.9 KB
sha256:673453913bbf52bed5473524760db2de948dbbe0dacfe8ce6c95a155e66a8eec