Skip to content

Sibling errors should not be added after propagation #3127

Sibling errors should not be added after propagation

Sibling errors should not be added after propagation #3127

Triggered via pull request July 15, 2025 14:01
Status Success
Total duration 1m 41s
Artifacts 3

pull_request.yml

on: pull_request
Matrix: ci / test
ci  /  Lint source files
56s
ci / Lint source files
ci  /  Run integration tests
1m 4s
ci / Run integration tests
ci  /  Run fuzzing tests
26s
ci / Run fuzzing tests
ci  /  Check for commonly ignored files
5s
ci / Check for commonly ignored files
ci  /  Check health of package-lock.json file
23s
ci / Check health of package-lock.json file
ci  /  Measure test coverage
34s
ci / Measure test coverage
ci  /  Run CodeQL security scan
1m 37s
ci / Run CodeQL security scan
Security check of added dependencies
4s
Security check of added dependencies
Diff content of NPM package
51s
Diff content of NPM package
ci  /  Build 'npmDist' artifact
26s
ci / Build 'npmDist' artifact
ci  /  Build 'denoDist' artifact
20s
ci / Build 'denoDist' artifact
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
ci / Run CodeQL security scan
Unable to validate code scanning workflow: MissingPushHook
ci / Run CodeQL security scan
1 issue was detected with this workflow: Please specify an on.push hook to analyze and see code scanning alerts from the default branch on the Security tab.

Artifacts

Produced during runtime
Name Size Digest
denoDist
183 KB
sha256:39d031e0259f439ed7ff53d099b9891bc49a216b097b471c05948623fc188adc
npm-dist-diff.html
1.98 KB
sha256:db23f2a9ec6514b11141caed27b60569f57018852170cd18dbb648a9269b3c78
npmDist
412 KB
sha256:c52ddea91f8b88deca020ec55aea5a33148b299dcb030ce3315175ce2c6f7de2