Skip to content

fix: change order of steps in workflow #3

fix: change order of steps in workflow

fix: change order of steps in workflow #3

Triggered via push September 21, 2024 16:21
Status Failure
Total duration 41s
Artifacts

main.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

1 error and 2 warnings
build
Error: Command failed: git push heroku HEAD:refs/heads/main --force remote: Updated 87 paths from 834e96a remote: Compressing source files... done. remote: Building source: remote: remote: -----> Building on the Heroku-22 stack remote: -----> Using buildpack: heroku/nodejs remote: -----> App not compatible with buildpack: https://buildpack-registry.s3.amazonaws.com/buildpacks/heroku/nodejs.tgz remote: remote: ! ERROR: Application not supported by 'heroku/nodejs' buildpack remote: ! remote: ! The 'heroku/nodejs' buildpack is set on this application, but was remote: ! unable to detect a Node.js codebase. remote: ! remote: ! A Node.js app on Heroku requires a 'package.json' at the root of remote: ! the directory structure. remote: ! remote: ! If you are trying to deploy a Node.js application, ensure that this remote: ! file is present at the top level directory. This directory has the remote: ! following files: remote: ! remote: ! backend/ remote: ! frontend/ remote: ! package-lock.json remote: ! README.md remote: ! remote: ! If you are trying to deploy an application written in another remote: ! language, you need to change the list of buildpacks set on your remote: ! Heroku app using the 'heroku buildpacks' command. remote: ! remote: ! For more information, refer to the following documentation: remote: ! https://devcenter.heroku.com/articles/buildpacks remote: ! https://devcenter.heroku.com/articles/nodejs-support#activation remote: remote: remote: More info: https://devcenter.heroku.com/articles/buildpacks#detection-failure remote: remote: ! Push failed remote: ! remote: ! ## Warning - The same version of this code has already been built: 518f5147b8734ddd952ff19f2ac3cf279e6581e0 remote: ! remote: ! We have detected that you have triggered a build from source code with version 518f5147b8734ddd952ff19f2ac3cf279e6581e0 remote: ! at least twice. One common cause of this behavior is attempting to deploy code from a different branch. remote: ! remote: ! If you are developing on a branch and deploying via git you must run: remote: ! remote: ! git push heroku <branchname>:main remote: ! remote: ! This article goes into details on the behavior: remote: ! https://devcenter.heroku.com/articles/duplicate-build-version remote: remote: Verifying deploy... remote: remote: ! Push rejected to jetedge-test. remote: To https://git.heroku.com/jetedge-test.git ! [remote rejected] HEAD -> main (pre-receive hook declined) error: failed to push some refs to 'https://git.heroku.com/jetedge-test.git'
build
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
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/