fix(cli): benchmark workflow and action#73
Merged
Merged
Conversation
15c72d0 to
eed3e37
Compare
CI Summary
Deploy UI — Passed
Deploy Example — Passed
Labelsscope: benchmark |
andrew-ifrita
approved these changes
Apr 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Fix two CI benchmark workflow failures:
@parity/dotns-cli) by default, with GitHub release tarball as fallbackauthorizejob inbenchmark-on-demand.yml, fixing "Missing WebSocket class" error frompolkadot-api/ws-providerType
Package
@parity/dotns-cliRelated Issues
Fixes
Missing WebSocket classChecklist
Code
bun run lintpassesbun run formatpassesbun run typecheckpassesDocumentation
Breaking Changes
Breaking changes:
Testing
How to test:
authorizejob should pass without "Missing WebSocket class"Notes
npm install -g @parity/dotns-clifirst, falling back to the GitHub release tarball if npm failsauthorizejob was the only workflow missingsetup-node@v4withnode-version: "22"— all other workflows (deploy.yml,daily-deploy-sized-benchmarks.yml) already had it