Configure gh action deployments from main · NYCPlanning/labs-zap-search@c035570

Triggered via push October 11, 2024 17:27

main

Status Failure

Total duration 4m 32s

Artifacts –

staging.yml

on: push

1 error and 9 warnings

Error: Command failed: heroku create staging-zap-search --team *** /bin/sh: 1: heroku: not found

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

🧪 Test client code: client/tests/acceptance/542-document-upload-for-recommendation-test.js#L174

Unexpected console statement

🧪 Test client code: client/app/adapters/application.js#L14

Unexpected console statement

🧪 Test client code: client/app/components/reviewed-project-card.js#L30

Unexpected console statement

🧪 Test client code: client/app/controllers/my-projects/assignment/hearing/add.js#L128

Unexpected console statement

🧪 Test client code: client/app/routes/my-projects/assignment.js#L14

Unexpected console statement

🧪 Test client code: client/app/routes/my-projects/assignment/hearing/add.js#L29

Unexpected console statement

Skip setting environment url as environment 'staging' may contain secret.