Skip to content

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

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

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

Triggered via pull request July 30, 2026 18:10
Status Success
Total duration 1m 48s
Artifacts 3

analyze.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

1 warning
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/

Artifacts

Produced during runtime
Name Size Digest
analysis_comment.txt
378 Bytes
sha256:5e993e12559e5cbf39e44250f851695cf55ece30dbd1b88208b0f725e631e5fd
bundle_analysis.json
330 Bytes
sha256:2260e8193a744af3f174d11d038aa8f0ba4f274fbb2805771a643a43007b6200
pr_number
139 Bytes
sha256:a2b6543ea0f32a3d752a811c3d4d4f22c3b0c568c4ff0b4a16eb561195fd5a44