Skip to content
w3up-client

fix(egress/record): rename capability #1260

Sign in to view logs

fix(egress/record): rename capability

fix(egress/record): rename capability #1260

Triggered via pull request November 5, 2024 19:09
@fforbeckfforbeck
synchronize #1572
fix/usage-record-definition
Status Success
Total duration 2m 25s
Artifacts –

w3up-client.yml

on: pull_request
Matrix: Test
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
Test (20): packages/w3up-client/src/account.js#L245
Defaults are not permitted on @param
Test (20): packages/w3up-client/src/account.js#L246
Defaults are not permitted on @param
Test (20)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Test (18): packages/w3up-client/src/account.js#L245
Defaults are not permitted on @param
Test (18): packages/w3up-client/src/account.js#L246
Defaults are not permitted on @param
Test (18)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/