Skip to content

fix: make backlog grooming reflect what actually blocks an issue (#623) #1168

fix: make backlog grooming reflect what actually blocks an issue (#623)

fix: make backlog grooming reflect what actually blocks an issue (#623) #1168

Triggered via push August 17, 2026 12:21
Status Success
Total duration 6m 27s
Artifacts

ci.yml

on: push
Detect changes
6s
Detect changes
Code quality
17s
Code quality
Fast tests
2m 3s
Fast tests
Algorithm tests
0s
Algorithm tests
Frontend checks
2s
Frontend checks
E2E tests
6m 9s
E2E tests
Docker build & boot
2m 23s
Docker build & boot
Merge gate
2s
Merge gate
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Detect changes
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: dorny/paths-filter@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Code quality
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/setup-python@v5. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Fast tests
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/setup-python@v5. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
E2E tests
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/setup-node@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/