Skip to content

feat: migrate on npm and update design system #3

feat: migrate on npm and update design system

feat: migrate on npm and update design system #3

Triggered via pull request January 4, 2024 14:17
Status Failure
Total duration 4m 6s
Artifacts
setup  /  setup-nodejs-and-install-dependencies
19s
setup / setup-nodejs-and-install-dependencies
checks-and-tests  /  ...  /  setup-nodejs-and-install-dependencies
19s
checks-and-tests / setup / setup-nodejs-and-install-dependencies
checks-and-tests  /  validate-markdown
24s
checks-and-tests / validate-markdown
checks-and-tests  /  eslint
43s
checks-and-tests / eslint
checks-and-tests  /  stylelint
23s
checks-and-tests / stylelint
checks-and-tests  /  compile
22s
checks-and-tests / compile
checks-and-tests  /  test
21s
checks-and-tests / test
checks-and-tests  /  build
58s
checks-and-tests / build
checks-and-tests  /  build-storybook
36s
checks-and-tests / build-storybook
deploy  /  ...  /  setup-nodejs-and-install-dependencies
37s
deploy / setup / setup-nodejs-and-install-dependencies
deploy  /  deploy-website
1m 13s
deploy / deploy-website
deploy  /  deploy-storybook
51s
deploy / deploy-storybook
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 warning
deploy / deploy-website
Input required and not supplied: aws-region
deploy / deploy-website
The following actions uses node12 which is deprecated and will be forced to run on node16: aws-actions/configure-aws-credentials@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/