Skip to content
CI

Clarify that RP can use its own credentials even if extension not specified #441

Sign in to view logs

Clarify that RP can use its own credentials even if extension not specified

Clarify that RP can use its own credentials even if extension not specified #441

Triggered via pull request August 13, 2024 16:29
@ianbjacobsianbjacobs
opened #272
rp-credentials-enabled
Status Failure
Total duration 47s
Artifacts –

build.yml

on: pull_request
Build, Validate, and Publish
38s
Build, Validate, and Publish
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 2 warnings
Build, Validate, and Publish
Process completed with exit code 2.
Build, Validate, and Publish
Failed. See details above.
Build, Validate, and Publish
Process completed with exit code 1.
Build, Validate, and Publish
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build, Validate, and Publish
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/