Skip to content

Clarify why fetching stays in the Effect in "Fetching data" #7741

Clarify why fetching stays in the Effect in "Fetching data"

Clarify why fetching stays in the Effect in "Fetching data" #7741

Triggered via pull request July 30, 2026 17:57
Status Success
Total duration 2m 5s
Artifacts 3

analyze.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
analyze
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4, dawidd6/action-download-artifact@268677152d06ba59fcec7a7f0b5d961b6ccd7e1e. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
analyze
Failed to restore:

Artifacts

Produced during runtime
Name Size Digest
analysis_comment.txt
378 Bytes
sha256:5c22c64e60ec2a6bf8364e77e8bff885d15c704836c0807e410c5d2219ac9e4d
bundle_analysis.json
330 Bytes
sha256:e9d2a0012913e3c799185ba841dc354d43a4dfdde39e4d9736559340dabe7c69
pr_number
139 Bytes
sha256:dc99e82933f2df142c3de5185ac94a3ddefe94d9a37e4dab7da45a5286de7832