Add workflow for deploying to a staging website #3
brandonpaytondeploy-website-to-staging.yml
on: pull_request
deploy-to-staging
/
build_and_deploy
4m 45s
Annotations
1 error and 3 warnings
|
deploy-to-staging / build_and_deploy
Process completed with exit code 255.
|
|
deploy-to-staging / build_and_deploy
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v2, actions/upload-artifact@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
deploy-to-staging / build_and_deploy
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, actions/cache@v2, actions/upload-artifact@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Deprecation notice: v1, v2, and v3 of the artifact actions
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "playground-website".
Please update your workflow to use v4 of the artifact actions.
Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
playground-website
Expired
|
340 MB |
|