Skip to content

chore: Get rid of registry deployment component #1539

chore: Get rid of registry deployment component

chore: Get rid of registry deployment component #1539

Triggered via pull request August 7, 2024 13:06
@tolushatolusha
reopened #2909
23026
Status Success
Total duration 2m 2s
Artifacts

pr-check.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

7 warnings
license-validation
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, actions/setup-go@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
unit-tests
The following actions uses Node.js version which is deprecated 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/
unit-tests: src/hooks/analytics/segment-adapter.ts#L26
Do not use "require"
unit-tests: src/utils/command-utils.ts#L72
Do not use "__dirname"
unit-tests: src/utils/utls.ts#L25
Do not use "require"
unit-tests: src/utils/utls.ts#L69
Do not use "__dirname"
readme-md-validation
The following actions uses Node.js version which is deprecated 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/