Heroku: Hosting The Next.Js Frontend App #63
Triggered via workflow run
June 2, 2024 16:11
ShamaKamina
completed
5874169
Status
Failure
Total duration
41s
Artifacts
–
hosting-frontend.yml
on: workflow_run
deploy-frontend
32s
Annotations
1 error and 3 warnings
deploy-frontend
Error: Command failed: git push heroku HEAD:refs/heads/main --force
remote: Updated 148 paths from 4faba60
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: ! docker/
remote: ! documentation/
remote: ! frontend/
remote: ! README.md
remote: ! reverseproxy/
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: 5874169e194a3757752d297d55e03181c62e79fc
remote: !
remote: ! We have detected that you have triggered a build from source code with version 5874169e194a3757752d297d55e03181c62e79fc
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 ***.
remote:
To https://git.heroku.com/***.git
! [remote rejected] HEAD -> main (pre-receive hook declined)
error: failed to push some refs to 'https://git.heroku.com/***.git'
|
deploy-frontend
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, akhileshns/heroku-deploy@v3.12.12. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
deploy-frontend
The following actions uses node12 which is deprecated and will be forced to run on node16: akhileshns/heroku-deploy@v3.12.12. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
deploy-frontend
Unexpected input(s) 'project_path', valid inputs are ['heroku_api_key', 'heroku_email', 'heroku_app_name', 'buildpack', 'branch', 'dontuseforce', 'dontautocreate', 'usedocker', 'docker_heroku_process_type', 'docker_build_args', 'appdir', 'healthcheck', 'checkstring', 'delay', 'procfile', 'rollbackonhealthcheckfailed', 'env_file', 'justlogin', 'region', 'stack', 'team']
|